Thoughts?

rbsec/sslscan
sslscan tests SSL/TLS enabled services to discover supported cipher suites
This usually means that you are attempting to talk HTTPS over a connection where the other side talks HTTP, e.g syncthing sends plain HTTP while your browser is trying to negotiate TLS (HTTPS).
The error still looks like itās going through https, given its a SSL error
Any recommendation on how to bypass the SSL forcing in the browser?
Did you try to explicitly prefix it with http:// ?
yes, it automatically reverts to https when I hit āEnterā
Sounds like an extension that forces https, or a recent change/update in your browser, that made forcing https the default. Iād expect a quick search for your browser name, https and āThis site canāt provide a secure connectionā to clear things up.
did you click on the button ālearn moreā? i think i remember having encountered such a message before and there were more options there. Not sure though. Foggy memories.
It was mentioned that the problem occurred in both Firefox, Chrome, and Safari though. This would indicate that it is likely not the browser. It could still be an extension though, if the same one is being used in all these browsers.
Does the same thing happen when using incognito/private browsing (where all extensions should be disabled by default)?
Yes, I receive the same error page on all browsers.
did you click on the button ālearn moreā? i think i remember having encountered such a message before and there were more options there. Not sure though. Foggy memories.
Yea, takes me to the same page that says nothing can be done about this error.
Could you check the certificate using the openssl cli command?
openssl s_client -connect 192.168.1.202:8384
Linux and maybe Mac should have it preinstalled.
Windows: Binaries - OpenSSLWiki
openssl s_client -connect 192.168.1.202:8384
Looks like it fails to find a cipher suite.
Could you try the following utility to check which ones are offered by the server?

sslscan tests SSL/TLS enabled services to discover supported cipher suites
Their release page has precompiled Windows binaries.
The handshake consisted of just 5 bytes and therefore whatever was send on the other side was probably broken.