Frndly TV for Channels

I got it, it deleted all of the " and re added them and it liked that. Thanks

2 Likes

It added the channels to the guide but when i try to play any of them it keeps saying "reconnecting". the error log says this:

2021/09/28 16:49:04.763645 [DVR] Fetching guide data for 20 stations in X-M3U @ 2021-10-11 4:30AM
2021/09/28 16:49:05.387320 [ERR] Failed to start stream for ch9333: M3U: Could not fetch playlist: http://127.0.0.1:8183/play/4: Get "http://127.0.0.1:8183/play/4": EOF
2021/09/28 16:49:05.431867 [HLS] Couldn't generate stream playlist for ch9333-dANY-ip192.168.4.62: M3U: Could not fetch playlist: http://127.0.0.1:8183/play/4: Get "http://127.0.0.1:8183/play/4": EOF
2021/09/28 16:49:05.432019 [HLS] Stopping transcoder session ch9333-dANY-ip192.168.4.62

I have verified the email and password and they work when i log into https://frndlytv.com/

3 Likes

I’m guessing maybe the 127.0.0.1 loop back address you’re using might be biting you. Might try it with the actual IP address of the server instead to see if it works.

1 Like

Matt, your work is awesome. I'm so happy you're in the CDVR community now. If you could create something like this for Stremium channels to get them into Channels DVR you'd be the best!

3 Likes

Thank you Matt. I updated and added the IP as you directed and works flawlessly. Thank you. This Local Now is better than the OTA channels I can recieve locally. The return of The Weather channel also is worth the subscrtiption. You rock.

3 Likes

OMG I cant believe I didn't see that!! Thanks

2 Likes

I updated to the IP of the server but it's showing this error now when i click on the channel to play it from the web guide:

" Failed to start stream for ch9329: M3U: Could not fetch playlist: http://192.168.4.50:8183/play/10: Get "http://192.168.4.50:8183/play/10": EOF"

This is also the error that shows on the docker log:

" ----------------------------------------

172.17.0.1 - - [29/Sep/2021 14:44:20] "GET /play/12 HTTP/1.1" 302 -

----------------------------------------

Exception happened during processing of request from ('172.17.0.1', 62716)

Traceback (most recent call last):

File "/usr/local/lib/python3.8/socketserver.py", line 683, in process_request_thread

self.finish_request(request, client_address)

File "/usr/local/lib/python3.8/socketserver.py", line 360, in finish_request

self.RequestHandlerClass(request, client_address, self)

File "/usr/local/lib/python3.8/socketserver.py", line 747, in __init__

self.handle()

File "/usr/local/lib/python3.8/http/server.py", line 427, in handle

self.handle_one_request()

File "/usr/local/lib/python3.8/http/server.py", line 415, in handle_one_request

method()

File "./app.py", line 93, in do_GET

routes[func]()

File "./app.py", line 107, in _play

self.send_header('location', data['response']['streams'][0]['url'])

KeyError: 'response'

----------------------------------------"

I got similar errors overnight. I wonder if it isn't refreshing the login/token/session as often as it needs to or something. I restarted the docker container and it started working again- we'll see if it dies again after being on for a while.

Tuned to a Channel this morning with Playback error showing on screen. Open the log file on Docker Container and had the same log error as you did. Restarted the container the issue cleared up and the channels tuned in. Does Fndly require a relogin after some time has expired.

2 Likes

I restarted the server and still have the same results :frowning:

1 Like

Maybe delete and recreate. Sounds like it got messed up earlier with the password issues. Or else your password has symbols that are causing it to still not work.

It appears the docker cotainer only works normally for a few hours. When I tuned in to the weather channels I got errors. Channel worked after I restarted the docker container.

1 Like

Just a quick glance at the code for this on GitHub makes me think that our guess is probably correct, and it just needs to be updated to re-authenticate when necessary. I'll bet it's something Matt can fix without too much trouble.

please try the latest images.

I'd love to see a log after 24 hour so I can confirm which re-login method is actually required.

1 Like

I have dowloaded and started the latest container. All Channels are working. I will post logs of any errors when they happen. Thanks Matt

Will do. Thanks for the great support!

1 Like

just posted another little update that removes the logging of the session id.
As that's essentially your auth token and should not be shared

1 Like

I just had to restart the container again because it got disconnected from Frndly TV. It's fine after restart for several hours (I don't know exactly how long).

I'm using Docker on Windows 10. What is the way to update to the latest image? Yesterday, I tried to delete the container and then reran the installation command as specified on Github but it didn't seem to download the new version and just somehow relaunched the local copy.

This is what I have:

Update After 12 hours. Looks like you nailed it Matt.


1 Like

Nice, @kennyb3653. I need to figure out how to use this new Docker image.