Can no longer access my local server nor router via Firefox
I can no longer access my local TrueNAS server nor router via Firefox. My current version is 133.0.3. Safari has no trouble. Firefox gives no warning, no Advanced button, no option to bypass security. All I get is: "Unable to connect An error occurred during a connection to 192.168.0.102.
The site could be temporarily unavailable or too busy. Try again in a few moments. If you are unable to load any pages, check your computer’s network connection. If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web."
I have tried so many settings, troubleshootings, workarounds, I can't begin to list them. It happens in troubleshooting mode. I have created SSL certificates on the server many different ways to no avail. I'm thinking I will have to abandon Firefox with it's obscure, no-way-through security. But I wanted to ask for help first. Please help.
All Replies (7)
One more piece of information. The server is set to accept either HTTP or HTTPS requests. Safari can connect either way. In Firefox, http simply changes to https when I try to connect, giving only the generic message above.
Go to about:config and check if dom.security.https_only_mode.upgrade_local = false.
Hi
This support article might help:
Yeah. The browser shouldn't switch to https with that.
Can you test it with mozregression? It would be helpful to find a rogue commit.
Paul said
Hi This support article might help: https://support.mozilla.org/en-US/kb/https-only-prefs#w_add-exceptions-for-http-websites-when-youre-in-https-only-mode
I don't understand that. HTTPS-only mode is currently disabled. So Firefox shouldn't be insisting on HTTPS. What would be the point of making an exception to it?
TyDraniu said
Can you test it with mozregression? It would be helpful to find a rogue commit.
Wow, that looks like a big project, especially because I'm on Mac, not Windows, so it would be all command line. And I have no idea how to identify a known "good" date. And is it even a known bug, not some setting problem?
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.