Frndly TV for Channels

No. that page won't load
Also it looked as if everything was pulling correctly until the end of the command chain when this pops up:
docker : Error response from daemon: No such container: frndlytv-for-channels
At line:2 char:1

  • docker stop frndlytv-for-channels
  •   + CategoryInfo          : NotSpecified: (Error response ...tv-for-channels:String) [], RemoteExcepti 
     on
      + FullyQualifiedErrorId : NativeCommandError
    
    

docker : Error: No such container: frndlytv-for-channels
At line:3 char:1

  • docker rm frndlytv-for-channels
  •   + CategoryInfo          : NotSpecified: (Error: No such ...tv-for-channels:String) [], RemoteExcepti 
     on
      + FullyQualifiedErrorId : NativeCommandError

Ok I got it fixed. I had to purge all the docker data and start fresh. Once I re-installed the container and added it back to the custom list all the channels re-appeared! Thanks for the assistance/support. I am a huge fan of Channels DVR ever since I finally was forced to ditch the old Tivo. The new Tivo stream 4k and Channels DVR are amazing combo!

1 Like

I have this working on my Windows Desktop Docker along with Channels DVR on a raspberry pi4. However, I am finding that Windows Desktop Docker is slowing down my pc. Is it possible to run this directly on the Channels DVR raspberry Pi4 without using Windows Desktop Docker? If so, can someone give me a step by step?

1 Like
  1. enable SSH on the Pi via the DVR web UI
  2. connect via SSH
  3. run the docker commands

Thanks! How do I determine the "PUBLIC part of my SSH key pair"?

Try this. I can walk through more if needed.

1 Like

Thanks for your help. I am close, but not quite there. I have generated the private and public keys, formatted the USB stick with the label config and put the authorized_keys file on it. I have inserted the usb stick into the RPI. I ran putty on PC, when I try to run a session for 192.168.1.253 I get a "network error: connection refused" message. I also tried enabling SSH via channel dvr settings by adding the numbers (I have put x instead of the numbers) from the public key file: rsa-key-xxxxxxxx", but I get the same connection refused error message.

If I try accessing it from the pc cmd prompt, ssh [email protected] -p 22222 results in "[email protected]: Permission denied (publickey).

UPDATE: Using Putty, I can now get to a screen that says "using username "root"; "server refused our key" . I got there by using putty, putting "[email protected]" port 22222 as the host name and adding the private key file under "ssh/authorization" page.

UPDATE 2: I am in!!! I think I might have been missing a character when pasting the public key to the dvr server page when enabling ssh access. I have to leave now, so I won't be able to try installing the frndly docker on the server until later today, but will report back.

1 Like

UPDATE 3: I have this working. Thanks Hancox for pointing me in the right direction.

1 Like

Good to hear. Sorry if the post was only loosely on topic

I'm running Channels DVR on Windows 10 and using the Python version of Frndly TV

Last night, the Frndly Hallmark channels stopped working with a FFmpeg/codec errors. Other Frndly TV channels are streaming just fine. I just updated the Channels DVR to the pre-release, but still get the error.
I can watch Hallmark via Frndly's website and with TVE.

/08/31 19:31:53.372092 [TNR] Opened connection to M3U-Frndly for ch9002 Hallmark Channel

2022/08/31 19:31:53.378864 [HLS] Starting live stream for channel 9002 from [127.0.0.1](http://127.0.0.1/) (bitrate=27641)

2022/08/31 19:32:03.806423 [HLS] Probe failed for live stream after 10.4264404s and 0 bytes

2022/08/31 19:32:08.145496 [HLS] Couldn't generate stream playlist for ch9002-dANY-ip127.0.0.1: Timeout waiting for session to start after 8s

2022/08/31 19:32:08.145496 [HLS] Stopping transcoder session ch9002-dANY-ip127.0.0.1 (out: 0s, finished: false)

2022/08/31 19:32:08.199958 [HLS] ffmpeg: ch9002-dANY-ip127.0.0.1-remux: pipe:: could not find codec parameters

2022/08/31 19:32:08.272686 [TNR] Closed connection to M3U-Frndly for ch9002 Hallmark Channel

2022/08/31 19:32:08.272686 [SNR] Buffer statistics for ch9002 Hallmark Channel: buf=0% drop=0%

2022/08/31 19:32:10.074740 [TNR] Opened connection to M3U-Frndly for ch9002 Hallmark Channel

2022/08/31 19:32:10.081953 [HLS] Starting live stream for channel 9002 from [127.0.0.1](http://127.0.0.1/) (bitrate=27641)

2022/08/31 19:32:16.920362 [NAT] Failed to discover upnp routers

2022/08/31 19:32:16.920362 [NAT] Failed to discover router using natpmp and upnp.

2022/08/31 19:32:17.337963 [HLS] Couldn't generate stream playlist for ch9002-dANY-ip127.0.0.1: Timeout waiting for session to start after 8s

2022/08/31 19:32:17.337963 [HLS] Stopping transcoder session ch9002-dANY-ip127.0.0.1

2022/08/31 19:32:17.536952 [HLS] Probe failed for live stream after 7.4544916s and 0 bytes

2022/08/31 19:32:17.542209 [HLS] ffmpeg: ch9002-dANY-ip127.0.0.1-remux: pipe:: could not find codec parameters

2022/08/31 19:32:17.582332 [TNR] Closed connection to M3U-Frndly for ch9002 Hallmark Channel

2022/08/31 19:32:19.087071 [TNR] Opened connection to M3U-Frndly for ch9002 Hallmark Channel

2022/08/31 19:32:19.093551 [HLS] Starting live stream for channel 9002 from [127.0.0.1](http://127.0.0.1/) (bitrate=27641)

2022/08/31 19:32:21.799057 [HLS] Stopping transcoder session ch9002-dANY-ip127.0.0.1

2022/08/31 19:32:23.454983 [HLS] Probe failed for live stream after 4.3612397s and 0 bytes

2022/08/31 19:32:23.459162 [HLS] ffmpeg: ch9002-dANY-ip127.0.0.1-remux: pipe:: could not find codec parameters

2022/08/31 19:32:23.509117 [TNR] Closed connection to M3U-Frndly for ch9002 Hallmark Chann
1 Like

Yeah I noticed Hallmark channels (all 3) on Frndly went down the other night. It happened a couple of months ago too, took about a week for it to resolve itself on its own. A couple of things I can tell you is that it is not a ChannelsDVR problem. It also is not a TVE issue, because Frndly isn't TVE. So the standard TVE troubleshooting won't work. I have noticed that the Hallmark Channels on the Frndly Official apps are showing in SD while all the other Frndly channels are displaying HD.

So my belief is that Frndly is having a problem with the Hallmark HD Streams. Their officials apps will automatically switch to SD. The unofficial Frndly TV for Channels docker here I believe only pulls the HD streams from Frndly. Maybe @matthuisman can confirm that is how it functions.

This is my best guess at this time. But maybe some other people far brighter than me can shine some light on the issue. I am basically hoping that it will resolve itself like it did last time.

1 Like

Thanks - Guess it's good to know that it's not a problem with my setup. But I do have another provider (which is where my TVE is coming from).

Yeah, it took me a while to realize those Hallmark channels had gone rouge again because Channels automatically switched to my Spectrum account after not being able to use the Frndly account for Hallmark. So bravo to Channels for working perfectly and finding a working source.

3 Likes

Happy Saturday everyone. For some reason Docker on my Mac Mini was eating RAM...so I removed it and would like to try the Python3 method.
I am in terminal and it appears I have xcode already...I read that was needed? Do I install Python3 from terminal....or? Sorry for the remedial questions.

I just noticed since Sept 1st 2022 that I am getting "403 Forbidden" errors on all three Hallmark channels. Is this the same thing you are talking about. Will this go away on it's own or is there something I need to do, beyond restarting everything?

I am pretty sure this is something we will have to wait for Frndly to figure out. I checked their official apps today and those channels are still SD there too (everything else HD). My current theory (recap) is Frndly is having problems with Hallmark HD streams, and the Frndly TV for Channels docker only uses the HD streams, so Hallmark is currently unavailable to us. The last time this came up it resolved itself in a week or two. That is the best I can figure.

can someone please try latest code / docker container and see if that fixes Hallmark

1 Like

All three Hallmarks appear to be working now on latest container.

1 Like

I know this can not be related to what @matthuisman did with the container, but the Hallmark Channels in the official apps are now also showing HD streams again. During the down time, in the official apps the Hallmarks were in the 1.2m bitrate range, now they are in 3.25m bitrate range.

UPDATE: Hallmark is again not running on Channels. And is back to SD in the official Apps. Hallmark Drama and Hallmark Movies and Mysteries are still running on Channels and still HD in official Apps.

Is there anyone that might be able to help me get FRNDLY into my Channels DVR via python on my MacMini?