Closed paul-chambers closed 4 years ago
This will probably be addressed by removing the IPTV-EPG custom provider since there's no particular advantage to using it over the custom provider, which does work.
named providers will be removed from the next release; they don't add any value at this point.
telly release with the issue: telly, version 1.1.0.6 (branch: dev, revision: dafac1f21a0f5397511965d9f0a2ae930d51fe95) build user: root@c8b3d5116b6b build date: 20190509-14:43:23 go version: go1.12.5
Last working telly release (if known): unknown
Operating environment (Docker/Windows/Linux/QNAP, etc.): Linux: Ubuntu 18.04 inside a KVM virtual machine
Description of problem:
The 'IPTV-EPG' provider no longer works. This appears to be because IPTV-EPG is now using Cloudflare, and Telly isn't providing a 'host' header when making the HTTP request, so Cloudflare doesn't know which HTTP host the request is for.
If I use the 'Custom' provider, and provide the M3U and EPG URLs explicitly, Telly does start successfully.
Contents of
telly.config.toml
[if you're using a version above 1.1]:Command line used to run telly [if applicable]:
telly or docker log:
and then crickets...
Additional information: