curl -XPOST http://x.x.x.x:8089/providers/m3u/sources/(M3U-NAME HERE)/refresh
Put this in a .bat file or python script to run as often as you need.
2 Likes
Thanks for your help! I tried creating a batch file with this inside.
curl -XPOST http://192.168.1.6:8089/providers/m3u/sources/myfile.m3u8/refresh
it just says false. is this the correct syntax?
:start
@echo -------------------------------------------------
@echo Start %date% %time%
curl -XPOST http://127.0.0.1:8089/providers/m3u/sources/test3/refresh
TIMEOUT /T 10740 /NOBREAK
goto start
This is the bat file I use. test3 is the name of the of the source in channels not the actual m3u file. It will send the command every 3 hours minus 1 minute. It worked fine when I was testing it. I stopped using it when I incorporate it in a python script.
The curl command and the http url are part of a single line in the file
1 Like
Thanks!
Does this mean it'll update in another 3 hours 1 minute? The false below the URL kind throwing me off.
1 Like
Token just expired so I can verify it did not work.
I am browsing to http://192.168.1.6:8089/providers/m3u/sources/ and nothing comes up? I try redacting all the way up to providers (ie: 192.168.1.168.1.6:8089/providers and get 404 errors. I feel like I am still missing something.
It would be easier to click the reload M3U button on the web UI then look at the browser developer network console to see what the correct URL is.
Using tmm1 suggestion I found the correct URL for the curl PS did not include /refresh - This was my problem. Removing it , I was able to successfully refresh the source and do so from PowerShell via a schedule of my own design. Thank you all.
1 Like
Well , I was wrong. Feeds still not be updating. Back to the drawing board...
The /refresh is definitely required.
When I plop the URL into my browser I get a 404 page. I'm not sure what I am doing wrong. I used the dev tools to pull that exact link per your instruction.
http://127.0.0.1:8089/providers/m3u/sources/mym3u/refresh
1 Like
Try using a command line client, and using the POST method; web browsers use GET when you use the address field.
1 Like
Tried that just now. I got
curl: (5) could not resolve proxy: post
1 Like
If you're on windows, make sure you use curl.exe not curl.
1 Like
I get the same results with and without curl.exe
curl.exe post http://192.168.1.6:8089/providers/m3u/sources/mym3u/refresh
curl: (6) Could not resolve host: post
404 Not Found
2 Likes
You have to use -XPOST like in all the examples above.
I've tried that too , with that I get
curl.exe -xpost http://192.168.1.6:8089/providers/m3u/sources/mym3u/refresh
curl: (5) Could not resolve proxy: post
1 Like
Doesn't match what I pasted. -X is not the same as -x and POST is not the same as post.
-x, --proxy [protocol://]host[:port]
Use the specified proxy.
-X, --request <command>
1 Like
Your capitalization is wrong. These details matter.
I think that was it..... bloody hell. Thank you all. I'll let you know.
Not sure of your background but I know for me when I first started dabbling in Linux after growing up with windows the most jarring thing was that everything is case-sensitive. Still burns me sometimes. 