Anybody else seeing issues launching the webUI in Chrome?
192.168.20.230 normally uses encryption to protect your information. When Chrome tried to connect to 192.168.20.230 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 192.168.20.230, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.
You cannot visit 192.168.20.230 right now because the website sent scrambled credentials that Chrome cannot process. Network errors and attacks are usually temporary, so this page will probably work later.
I also noticed that when you try to open the ui, it forwards to port 6238 not the listed 6237 on the settings page.
UI opens after SSL exception in Firefox with no issues. Still forwards to 6238 though. Not sure if this matters or not, but something I noticed.
[Plugin] unbalanced
in Plugin Support
Posted