Blue Iris, stunnel, and Chrome

jasauders

Getting the hang of it
Joined
Sep 26, 2015
Messages
214
Reaction score
56
Hi all. I'm having a bit of an issue with remoting in to my setup. I have a web server at home which also runs DDNS so I have a domain to hit my home network. I have an L2TP VPN set up through my Unifi USG, which works, and while I understand the VPN is more secure there are times I prefer to just lean on the stunnel route.

The thing is... my stunnel setup appears to be working. Firefox responds fine. Edge responds fine. Granted, I sometimes get the self signed cert error that I have to override, but with minimal fuss I can get Firefox to light up fine with the UI3 page.

Chrome on the other hand is displaying an error page citing ERR_SSL_VERSION_INTERFERENCE. I read about disabling the TLS hardening in chrome://flags when this error is received but no dice. I deleted all cache in Chrome and even deleted the user profile and reinstalled to start fresh. No dice.

Chrome is not my primary browser, but having read that Chrome is best used with UI3 I've found myself basically using Chrome as my BI browser. I also tested Brave and Opera, both of which failed (both of which are Chromium based). Makes me wonder.

Is anybody having issues with Chrome responding in this way? In particular I'm using version 73.0.3683.86 on Windows 10 1809.
 

jasauders

Getting the hang of it
Joined
Sep 26, 2015
Messages
214
Reaction score
56
You're wonderful. That worked well! :)

Because I'm a curious person, what's the bottom line of what happened here? Chrome dropped support (of any type) for TLS 1.3 and I assume the .pem stunnel creates is TLS 1.3? In contrast the free self signed cert service zerossl that you linked offers self signed certs of a higher level that can be plugged in to a stunnel environment, thus bypassing the problem altogether?
 

jasauders

Getting the hang of it
Joined
Sep 26, 2015
Messages
214
Reaction score
56
Hm, hey, did you by chance happen to try the camera/snapshot button within UI3? I did on accident when trying to click on the 3 dots next to it...

upload_2019-3-28_22-3-44.png
 

Walrus

Getting comfortable
Joined
Nov 19, 2018
Messages
593
Reaction score
449
Location
Ontario
You're wonderful. That worked well! :)

Because I'm a curious person, what's the bottom line of what happened here? Chrome dropped support (of any type) for TLS 1.3 and I assume the .pem stunnel creates is TLS 1.3? In contrast the free self signed cert service zerossl that you linked offers self signed certs of a higher level that can be plugged in to a stunnel environment, thus bypassing the problem altogether?
I could be wrong, but I think it's the other way around, as TLS 1.3 is the latest SSL version. Chrome removed support for disabling TLS 1.3. Stunnel creates a certificate that is less than TLS 1.3. ZeroSSL creates a TLS 1.3 cert. Again.. just guessing.

Hm, hey, did you by chance happen to try the camera/snapshot button within UI3? I did on accident when trying to click on the 3 dots next to it...

View attachment 40898
I just tried the button, and it works for me.
 
Top