Open issuer1 opened 5 years ago
I suspect that the problem isn't with the m3u3 port but that the browser is sending a referer
header whereas youtube-dl isn't. Try running youtube-dl with
--referer "http://driveproxy.net/drive/MlA3M2xCUmNSU3RlQWoyYW1HMllYQT09.html"
Checklist
Verbose log
Description
Downloading gives a 404 error in yt-dl but not in browser.
From another tool I know that this link refers to an m3u8 file on an url similar to this one: http://95.211.141.81:8080/hdplay-cache/eygdlhm7z2rmda63yoljex3wbqjds5dxbzezx2eqm3b2rrhg7bdqrk4a5jux6jc4sdgyaltbd7mayyasp77rt45zjvaroti6ombp2e7m2l3v5jodgkfntvqlckin3iicrzu5pm2g6n5wcds7jrve5mzzaic3ctuifzdfmghit747iu7st66lo3sdjzb7avhj3ymyqg5foa/hdplay.m3u8?SD
Beware however that the actual IP address changes all the time. With a browser I can download the m3u8 with no problems, but yt-dl cannot find it. It seems to ignore the fact that the URL needs to be found at port 8080 and not the default http-port. Seems like a pretty basic thing...