Port 8089 open but still getting the can’t connect message

I’m trying to connect the iOS app to my DVR while away from home. Never had a problem before today, but suddenly I’m getting the “Your Channels DVR Server at home can not be reached.” port 8089 error.

The problem is that port 8089 is definitely open. I can access it remotely from any browser if I go directly or if I go to my.channelsdvr.net.

Any thoughts?

It looks like your SSL certs have expired. The DVR should have renewed them but seems to have failed for some reason. Does the Log tab of the DVR show any error messages about TLS?

Yes see below

2019/12/17 12:29:10 [TLS] Requesting certificate for 3a0ab150de77.channelsdvr.net

2019/12/17 12:30:43 [ERR] Generating SSL cert failed: acme: Error -> One or more domains had a problem:
[3a0ab150de77.channelsdvr.net] time limit exceeded: last error: could not determine authoritative nameservers
2019/12/17 13:12:04 [NAT] Successfully mapped port 8089 using natpmp
2019/12/17 14:12:04 [NAT] Successfully mapped port 8089 using natpmp
2019/12/17 15:12:04 [NAT] Successfully mapped port 8089 using natpmp
2019/12/17 15:30:44 [TLS] Requesting certificate for 3a0ab150de77.channelsdvr.net
2019/12/17 15:32:17 [ERR] Generating SSL cert failed: acme: Error -> One or more domains had a problem:
[3a0ab150de77.channelsdvr.net] time limit exceeded: last error: could not determine authoritative nameservers
2019/12/17 16:12:04 [NAT] Successfully mapped port 8089 using natpmp
2019/12/17 16:47:23 http: TLS handshake error from 172.58.27.28:21495: EOF
2019/12/17 16:47:31 http: TLS handshake error from 172.58.27.28:32728: EOF
2019/12/17 16:47:33 http: TLS handshake error from 52.91.34.86:43658: remote error: tls: expired certificate
2019/12/17 16:47:46 http: TLS handshake error from 172.58.27.28:64028: EOF
2019/12/17 16:47:52 http: TLS handshake error from 172.58.27.28:61093: EOF
2019/12/17 16:47:59 http: TLS handshake error from 172.58.27.28:43711: EOF
2019/12/17 16:49:01 http: TLS handshake error from 172.58.27.28:54414: EOF
2019/12/17 16:49:05 http: TLS handshake error from 52.91.34.86:46898: remote error: tls: expired certificate
2019/12/17 16:49:12 http: TLS handshake error from 52.91.34.86:47232: remote error: tls: expired certificate
2019/12/17 16:51:12 http: TLS handshake error from 172.58.27.28:52319: EOF
2019/12/17 16:51:17 http: TLS handshake error from 172.58.27.28:40596: read tcp 192.168.2.227:8089->172.58.27.28:40596: read: connection reset by peer
2019/12/17 16:51:19 http: TLS handshake error from 172.58.27.28:63649: EOF
2019/12/17 16:51:28 http: TLS handshake error from 172.58.27.28:46181: EOF
2019/12/17 16:51:28 http: TLS handshake error from 52.91.34.86:52362: remote error: tls: expired certificate
2019/12/17 16:52:11 http: TLS handshake error from 52.91.34.86:54080: remote error: tls: expired certificate
2019/12/17 16:53:03 http: TLS handshake error from 52.91.34.86:56528: remote error: tls: expired certificate
2019/12/17 16:53:12 http: TLS handshake error from 52.91.34.86:56920: remote error: tls: expired certificate
2019/12/17 16:54:53 http: TLS handshake error from 172.58.27.28:30442: EOF
2019/12/17 16:54:54 http: TLS handshake error from 172.58.27.28:41900: EOF
2019/12/17 16:56:51 http: TLS handshake error from 52.91.34.86:37486: remote error: tls: expired certificate
2019/12/17 16:58:03 http: TLS handshake error from 52.91.34.86:40552: remote error: tls: expired certificate
2019/12/17 17:01:38 http: TLS handshake error from 52.91.34.86:50456: remote error: tls: expired certificate
2019/12/17 17:01:42 http: TLS handshake error from 52.91.34.86:50640: remote error: tls: expired certificate
2019/12/17 17:07:29 http: TLS handshake error from 52.91.34.86:37082: remote error: tls: expired certificate

Please click-and-hold on the Check for Update button

1 Like

All better now. Thanks!

1 Like

I’ve had this numerous times as well recently.

@tmm1, was there something you did as an update to the Channels DVR to fix this, or is there something (SSL Certs?) I should check and/or fix from here? Combination of both?

There was a fix recently, based on similar reports with the "could not determine authoritative nameservers" message

1 Like