I'm sorry. I don't have a clue what you just said here. I understand the pre-release version. Everything after that is a bit to vague for me to understand
Do you use a m3u url as your source? If there is a port in the url it may not process it properly
For instance, if you use m3u and anywhere in your process the m3u has a port 80 like this:
https://myprovider.com:80/mytv.php?type=m3u_plus&output=ts
Remove the port number from the url.
https://myprovider.com/mytv.php?type=m3u_plus&output=ts
That change and using the prerelease should solve the issue.
Ah, I understand now. No, that was not the problem. I was able to upgrade the container using the Server Information pull down. After that, it began to work.
Thank you for your massive assistance!
1 Like
Channels should support custom tags in m3u files used to fetch streams like User-Agent or Referer. I have to fiddle with nginx config used as a forward proxy to overcome this.
Did this get reverted recently @eric? I'm getting 461 again and after some debugging in my docker container shell, I tested a bunch of different user agents, including dummy ones, null ones, and VLC ones, all of them worked fine. However, when I specifically tried the user agent: Go-http-client/1.1 is when I received 461. I suppose it's possible whatever non default user agent channels uses got blacklisted but it feels less likely the case 
Edit: adding custom user agent to m3u works, meaning channels added support for custom user agents. see my post here Stream fails in Channels app and Chrome but works in VLC - #35 by addd45
No, nothing has been reverted.