Tablo Custom Channels Error

Playground Custom Channels
#1

Talbo running in Docker enter into to custom channels and gets this error!

tablo Error

1 Like
#2

Usually means the docker isn't running

#4

Is docker and Channels running on the same machine?

#6

Check the docker logs then maybe the container is having some issue

#7

no error in Tablo log on Docker

#8

Try rebooting the tablo?

#9

I rebooted Tablo, but it's still not cooperating. It is the only one of my docker that will not work now on Channels kind of odd since it was working before,

#10

Can you view/download the playlist from a brower and see what's in it?
http://{Tablo_for_Channels_docker_ip:port}/playlist.m3u

#12

Since this is internal on your LAN, you don't have to hide the ip address or port# since nobody can access that from the internet.

What do you see in a browser at this url?
http://{Tablo_for_Channels_docker_ip:port}

#14

So using a browser and going to http://127.0.0.1:8050 should bring up the status page for the Tablo for Channels docker container which should show the playlist url http://127.0.0.1:8050/playlist.m3u

Does it?

Of course if your browser isn't on the same device as the docker container you need to replace the local loopback IP (127.0.0.1) with the actual IP address (like 192.168.0.24) of the device running the docker container.

1 Like
#16

Was waiting for a reply

#18

And that url http://127.0.0.1:8050/playlist.m3u is what you're putting in the Channels DVR custom m3u Source URL field?
Screenshot 2022-10-13 at 18-19-01 Channels Settings

If true and looking at http://127.0.0.1:8050/playlist.m3u in a browser shows the playlist with your channels in it, it means the Tablo docker container is working and you configured the Channels DVR M3U source correctly.

#19

When I tried the 127 playlist I still receiving this error invalid source url context deadline exceeded (Client.Timeout exceeded while awaiting headers)

#20

You said you tried the 192 ip address. What exact url did you use?
Should be the IP address of the device running the docker container.
A 192.168.x.x IP address is private to your internal network, so don't worry about posting it.

It would help if you state the following;
what device the docker container is running on and its IP address
what device Channels DVR is running on and its IP address

#21

image
image1920×1280 145 KB

2 Likes
#24

That error is due to misconfigured DNS settings

#25
1 Like
#26

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.