8080 should be the port number after the colon, not 8090. and yes, you'll need to run docker-compose up -d again to recreate the container with the correct port forwarding.
Oops. Typo. I fixed that and going to run the command again.
1 Like
i think that will take care of it. let me know what happens...
The port for the channels dvr for the source and guide data should still be 8092?
I'm just wondering because I just put them in to save its taking a really long time to populate anything and channels dvr on my Shield TV is frozen at the same time....
yes. what that line in the docker-compose file is doing is telling the docker service that's running on your computer (at whatever IP you used) to forward port 8092 from the host to port 8080 inside the container. it's basically doing the same thing your router would do but on a smaller scale...
Just double checking. But, should it be taking so long to initially populate? This is what I've been seeing for a bit now
Pluto populated immediately, so just making sure this is normal...
something is still probably wrong, it should be quick. can you at least see the m3u and epg at the corresponding URLs now?
No. Same as before. Still says site can't be reached due to taking too long to respond...
there's still something wrong somewhere then, you need to be able to see those. if you can't see them, neither can channels.
i'm stumped at this point. i'll keep thinking but if anyone else has any ideas feel free to jump in...
So just making sure nothings off with anything I've entered. Here's a screenshot of my channels dvr server from before putting in the command.
I'm including it just to make sure that nothing is wrong in the compose file shown here
Or that these aren't wrong for the custom channel source and guide links: http://192.0.0.1:8092/m3u
what is the IP address of the server you're running this on?
Also what URL did you enter for Pluto?
1 Like
Then do the same thing for this one but with the new port, 8092
Where did 192.0.0.1 come from?
i am still not sure if using localhost or 127.0.0.1 for the APP_URL will work. it might if you're running it on the same server as channels, but i can't promise you it will (because i haven't tested it). that's why i said in the instructions to use the actual server IP there, because i know that will work.
The IP from the DVR screenshot shows 192.168.1.3
1 Like
@Mulliganman in that case, change the APP_URL env var to this:
APP_URL='http://192.168.1.3:8092'
1 Like
Like this shown here:
I put in the 127.0.0.1:8089 because I thought that's what you meant. I'm going to delete it from Docker Desktop again and will try to run the compose command again.
yep, exactly like that. you'll need to run the docker-compose up -d command again after changing it.
What should the source and guide data be?