Connection Lost Philo

I use channels through my Apple TV’s with a Synology server and Philo, Pluto, and a antenna. For the last couple of weeks the Philo part of my stream will randomly say “Connection Lost” it seems to happen quite a bit. This rarely if ever happened before. Does anyone have some insight on my issue? If I stream direct from the Philo app it’s fine and never has a issue.

Try updating your dvr to the latest prerelease

I've been having connection issues with Philo as well. The first month and a half it's been great but it's dropped on me twice in the last 4 days. It's not all Philo channels just certain ones like Food Network, HGTV, History, etc...
I get one of 3 errors "No Login Form Found", "404", or "Invalid Character <". My DVR server and Channels app on ATV are all up to date. When I delete Philo as a source and add it back that seems to fix it. But, this doesn't seem normal that I should have to do this so often.

Thanks, that seemed to fix my problem.

What version number are you running on your Channels DVR server?
2021.05.16.2133 is the current prerelease version

@chDVRuser 2021.05.16.2133 is the DVR Server version I’m running.

Great. Just checking :smile:
Many people have stated they're up to date, and are on the latest release version, not realizing how to get the latest prerelease.

I’m using Philo and on the latest prerelease (it’s 7/11 now, but I updated this morning and the latest is 7.10; was on the 7/9 prerelease version before this). Same setup as the original poster.

I’ve been getting “Connection Lost” after 30-45 minutes every time. Please advise, as I have a wife who is not happy (I.e. Wife Satisfaction Levels are low)

Also, each channel seems to take 5-10 seconds to connect. Not sure it’s related but advice on that would be helpful

Any errors in the DVR web ui log when this occurs? At first glance it sounds like a network or internet issue, but we need more details to confirm either way.

Besides the Channels DVR log entries that @Macnbaish mentioned, you should also mention which channels you're having the issue with.

Could be the networks feed has issues, i.e. Discovery Networks channel, etc. Logs will help in troubleshooting.

Hi again,

Thanks for the responses, and sorry for not having the chance to respond sooner.

As per the comments: Prior to posting yesterday, I too had a suspicion it might be related to my network; not sure if this matters any, but I am using an ethernet connection to both the Apple TVs I have where this is happening, so it isn't due to a wifi issue at least.

As for the channels it's happening on - I should preface things by saying that, in addition to having Philo as a source, I am using the Locast beta as a source for my locals; so maybe there things stem from the fact that I am using that...

Anyway, the "Connection Lost message happens pretty much on any channel; I could be on a Philo subscribed channel and it does this, but it happens just as much when I am using the Locast ones too.

As for logs - I don't know if you need more than this, but I did copy the logs from just before to just after the last "Connection Lost" message appears - definitely shows an error of some sort, but what exactly is beyond my knowledge of how this all works (sorry):

  • 2021/07/11 05:31:07.651941 [TNR] Opened connection to LOCAST-803 for ch4.2 KNBCDT2
  • 2021/07/11 05:38:47.371559 [TNR] Closed connection to LOCAST-803 for ch4.2 KNBCDT2
  • 2021/07/11 05:38:59.912163 [TNR] Opened connection to LOCAST-803 for ch9.2 KCALDT2
  • 2021/07/11 05:39:50.971967 [NAT] Successfully mapped port 8089 using natpmp
  • 2021/07/11 05:43:49.605949 [TNR] Opened connection to LOCAST-803 for ch13.1 KCOPDT
  • 2021/07/11 05:43:52.212364 [TNR] Closed connection to LOCAST-803 for ch9.2 KCALDT2
  • 2021/07/11 06:39:50.978689 [NAT] Successfully mapped port 8089 using natpmp
  • 2021/07/11 06:41:21.016006 [TNR] Closed connection to LOCAST-803 for ch13.1 KCOPDT
  • 2021/07/11 07:23:55.424680 http: TLS handshake error from 144.168.222.200:39981: tls: client offered only unsupported versions: []
  • 2021/07/11 07:24:50.247336 http: TLS handshake error from 144.168.222.200:37672: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:50.252036 http: TLS handshake error from 144.168.222.200:42409: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:50.298537 http: TLS handshake error from 144.168.222.200:37283: tls: client offered only unsupported versions: []
  • 2021/07/11 07:24:50.298647 http: TLS handshake error from 144.168.222.200:45093: tls: client offered only unsupported versions: [302 301]
  • 2021/07/11 07:24:50.298743 http: TLS handshake error from 144.168.222.200:32886: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:50.309147 http: TLS handshake error from 144.168.222.200:34951: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:51.699812 http: TLS handshake error from 144.168.222.200:41887: EOF
  • 2021/07/11 07:24:51.704406 http: TLS handshake error from 144.168.222.200:45502: EOF
  • 2021/07/11 07:24:52.706873 http: TLS handshake error from 144.168.222.200:34743: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:52.708177 http: TLS handshake error from 144.168.222.200:47803: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:52.723370 http: TLS handshake error from 144.168.222.200:35631: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:52.755545 http: TLS handshake error from 144.168.222.200:47835: tls: client offered only unsupported versions: [302 301]
  • 2021/07/11 07:24:54.277295 http: TLS handshake error from 144.168.222.200:46038: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:54.289081 http: TLS handshake error from 144.168.222.200:45225: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:55.165997 http: TLS handshake error from 144.168.222.200:46163: EOF
  • 2021/07/11 07:24:55.170941 http: TLS handshake error from 144.168.222.200:48420: tls: no cipher suite supported by both client and server
  • 2021/07/11 07:24:55.171029 http: TLS handshake error from 144.168.222.200:38466: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:55.173138 http: TLS handshake error from 144.168.222.200:43297: EOF
  • 2021/07/11 07:24:56.008741 http: TLS handshake error from 144.168.222.200:33311: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:56.015756 http: TLS handshake error from 144.168.222.200:43542: tls: client offered only unsupported versions: []
  • 2021/07/11 07:24:56.845213 http: TLS handshake error from 144.168.222.200:38882: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:56.853550 http: TLS handshake error from 144.168.222.200:45307: tls: client offered only unsupported versions: [301]
  • 2021/07/11 07:24:57.279032 http: TLS handshake error from 144.168.222.200:34710: tls: client offered only unsupported versions: []
  • 2021/07/11 07:39:50.987284 [NAT] Successfully mapped port 8089 using natpmp

Thanks in advance for your help :slight_smile:

Send logs through server software support - troubleshooting and submit Diagnostic Logs

Done. But as this is my first time doing this in a while, do I still need to email [email protected] as directed, or does me stating that I did that cover it?

We need diagnostics sent from the app after the error happens on the app.

Just submitted diagnostics 2x - once from the server page in my browser (which I realize now I shouldn't have done) and one from the app on the device I had the most recent "Connection Lost" message. Hopefully I did things right this time.