TLS handshake error: remote error: tls: bad certificate

Channels DVR Server Troubleshooting
#1

Seeing this error in the log.
TLS handshake error from 192.168.1.8:PORT#: remote error: tls: bad certificate
192.168.1.8 is my local PC I use to connect to the DVR web UI with.
PORT# of course changes with each error.

When I noticed it yesterday I refreshed the certificate on all three Channels DVR servers.
They are all now using a fresh xxxxxxxxxxxx.u.channelsdvr.net certificate.

I don't use and haven't enabled remote access on them (other than long enough to refresh the cert).

What in the DVR admin web UI would try to establish an https TLS connection to the server causing the errors?

#2

What url are you using to access the admin UI?

#3

I know what you're thinking, but I'm using http.
http://192.168.1.3:8089/ Synology NAS#1 running Channels Synology package with TVE source
http://192.168.1.3:8189/ Synology NAS#1 running Channels TVE docker with m3u source
http://192.168.1.4:8089/ Synology NAS#2 running Channels Synology package with HDHR Prime source

I could purposely cause that error by using https instead, but I have these bookmarked in my browser as http.

One strange thing is I have the error in the logs on all three of my Channels DVR's.
The other strange thing is the time of these errors are 2 somethimg PM.
Here's the logs from all three sorted by time where I added [IP:Port]

2021/05/20 14:17:34.270199 [192.168.1.3:8089] http: TLS handshake error from 192.168.1.8:61219: remote error: tls: bad certificate
2021/05/20 14:18:23.921633 [192.168.1.4:8089] http: TLS handshake error from 192.168.1.8:61233: remote error: tls: bad certificate
2021/05/20 18:44:39.720070 [192.168.1.3:8189] [SYS] Downloading new version v2021.05.21.0113
2021/05/20 18:45:25.275582 [192.168.1.3:8089] [SYS] Downloading new version v2021.05.21.0113
2021/05/20 18:45:50.323762 [192.168.1.4:8089] [SYS] Downloading new version v2021.05.21.0113
2021/05/21 14:18:52.610766 [192.168.1.3:8189] http: TLS handshake error from 172.18.0.1:34876: remote error: tls: bad certificate
2021/05/21 14:19:11.514411 [192.168.1.3:8089] http: TLS handshake error from 192.168.1.8:62662: remote error: tls: bad certificate
2021/05/21 16:19:05.828724 [192.168.1.3:8189] [TLS] Requesting certificate for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/21 16:24:42.943930 [192.168.1.3:8189] [TLS] Certificate ready for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/21 16:27:58.629338 [192.168.1.3:8089] [TLS] Requesting certificate for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/21 16:33:26.958101 [192.168.1.3:8089] [TLS] Certificate ready for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/21 16:39:47.469326 [192.168.1.4:8089] [TLS] Requesting certificate for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/21 16:45:21.993131 [192.168.1.4:8089] [TLS] Certificate ready for xxxxxxxxxxxx.u.channelsdvr.net
2021/05/22 14:14:55.637785 [192.168.1.3:8189] http: TLS handshake error from 172.18.0.1:35314: remote error: tls: bad certificate
2021/05/22 14:31:03.591917 [192.168.1.4:8089] http: TLS handshake error from 192.168.1.8:65354: remote error: tls: bad certificate
#4

You could always check and see which ports are open or listening on your server (as well as which clients are actually connected): netstat -na -f inet.

#5

The requests are coming from my Windows 10 laptop [192.168.1.8].
The 172.18.0.1 IP is my Docker bridge network on NAS#1.

I would have to run a continuous scan since these have so far only happened once each day in the last 3 days.

When I was refreshing the certificates on each I puposely connected using https to examine the certificates and the same exact error was logged. I did not include those in the list above since I know I caused it.

Thinking maybe it was a browser update causing it I checked my Firefox update history and see I've been running the latest release for the past 18 days.
Firefox 88.0.1 (64-bit) Build 20210504152106 installed on May 5, 2021 10:40:37AM