Frndly TV for Channels

What do you see at the container page http://192.168.11.224:8183

And did it get the correct username and password?
You can also view the container details from the Synology web UI
Docker > Container > Details
This will show the Environment Varialbles, so you can see what USERNAME and PASSWORD it got from the run command.

It doesn't seem to like port 8183. When it does show me what the playlist link is supposed to be it takes me to http://192.168.11.224:49163/. But it stops working after I try to run the command to feed the credentials. The credentials are correct.

To use the run command again you have to stop and delete the running container first.
Make sure you stop and delete all frndlytv-for-channels containers that are running, then do the run command again.
And to make sure you are using the latest version also delete the frndlytv-for-channels docker image before doing the run command again.

I deleted all the containers and redownloaded it from the repository.


I only have one instance running. This is what the log looks like:

I don't have a status page the local address using port 8183 or port 49156 where it was before. This is what I am running in the command line: "docker run -d --restart unless-stopped --env "USERNAME=-------------------" --env "PASSWORD=---------" --name frndlytv-for-channels -p 8183:80 matthuisman/frndlytv-for-channels"

No dice. I am stumped.

I appreciate your assistance to help me trouble shoot this so far. I don't know what else I can tell you to help me figure this out.

Sounds like you are running it twice.
The commandline docker run command will download the image, create the container and run it.
If you also did something in the Synology Docker app, you are duplicating things.

Stop and delete the container.
Delete the image.
Now Don't use the Synology Docker package to do anything this time.
Issue the docker run command.

Once it downloads and runs, then look at the Synology Docker app just to see what port it's running on.

1 Like

And I assume you know the basics.
To issue the docker run command you need to establish an SSH session to the Synology using something like putty.
The docker run command must be run as the root user.
So either sudo docker run ...
Or sudo - to establish a session as root.
Make sure to pay attention to any error messages you might get when doing the docker run command.

1 Like

I believe I did as you asked. I deleted everything out of the docker app, image and the container.



I then ssh'ed into the Synolgy nas and got this response:

And it looks like that works and solved all of the issues for the most part.


But the quide isn't quite there. I guess that will fill in as it downloads.

1 Like

Here's what I use for the custom channel setup.
The XMLTV guide data isn't needed as the playlist contains the station id's for guide mapping.
You should get 16 days of guide data that refreshes every morning between 9 and 11am.

I'll give that a try. I only had a few channels populate guide data after it parsed the information. I tried to the the guide data blank and it had a weird error and wouldn't play nice and let me re add the custom channel. So I deleted the whole thing from docker and reinstalled it and now the server is hung up trying to add the custom channel again. Still not pulling any guide data.


crash

Two things.
Make sure the only docker container running for frndlyTV is at port 8183.
Delete your custom source and add again using a different name than you used previously and my settings (except for IP of course).

For some reason when you edit a custom channel source, things from the original creation stick around and aren't actually changed when you edit. I find it best to delete it and re-create it using a slightly different name.

Just not your day today, huh?

It was a rough trip to get to the finish line. I appreciate your assistance. Chances are our back and forth on the forum will help others out as well. But it looks like we have success. I greatly appreciate your assistance. Thank you!

2 Likes

Aww… I missed all the fun. Well it looks like you got it.

Concerning those four ”special” channels (Dove , Curiosity, Dove Kids and Dove family) that are a pain with the guide. They don’t have gracenotes so they are not covered by the Channels built in .EPG.

In case anyone is curious on how to tidy that issue up a little bit. My setup I actually use 2 Frndly sources. One called Frndly exactly like @chDVRuser uses in their screen shot (except I block those four special channels). No .EPG specified. It’s important you do not add an XMLTV guide link. And do not bother trying to manually map those four channels from manage lineup, the data will be wrong.

Then I have a second source called FrndlyHard2Get with “http://192.168.1.241:8183/playlist.m3u8?include=frndly-38,frndly-49,frndly-16,frndly-50” and I use the docker provided epg.xml. In my case http://192.168.1.241:8183/EPG.xml. Note that using include will exclude everything else. You may also have to go into manage lineup manually map each channel.

Then I combine those two sources into a channel collection containing both sources. The “special” channels will at least have show titles and times but do not have descriptions. But at least you can set individual recordings on those channels.

1 Like

Good point.
You could also do it this way, and if frndly channel id's change, channels are dropped or added or gracenote station id's are found you wont have to change your settings.

1 Like

Oh awesome. I must have missed that back in the 100s.

Anyone else having problems with Frndly TV starting on yesterday? Things were a little wonky yesterday with channels and guide info, and then this morning not a single Frndly TV channel is accessible. I have made no changes to my setup at all. Only thing I can see is maybe there was something in the latest server update that broke it, as the only change in the system was the ChannelsDVR server software updated recently. This had been running rock solid since setup a few months ago.

Chief

Hi there,
Looks like Frndly TV went down.
The streams are slowly coming back up. Looks like a network backbone error. Services not related to FRNDLY are being affected.

1 Like

Yeah it looks like it’s down for me too. The Frndly Apple TV app is also down for me. And the Frndly live TV website is all screwed up. And so is the Frndly iOS app on iPad. So this is not an issue with @matthuisman FrndlyTV-for-channels Docker or the ChannelsDVR. This is completely on the Frndly end. Hopefully they will correct it soon.

Oh there is a notice on their website. Full Service Outage. They are aware of the issue. Frndly TV Service Status Page

Looks like FRNDLY TV is back online.
I suspect they may still may be working things out but the service appears to be back online.

Yup, it popped in and out until late this afternoon, back to normal now.

Chief