Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Can no longer access my local server nor router via Firefox

  • 9 odpowiedzi
  • 1 osoba ma ten problem
  • 244 wyświetlenia
  • Ostatnia odpowiedź od sites1
  • Rozwiązane

sites1
sites1

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.

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.

Wybrane rozwiązanie

This problem turned out to be due to an obscure macOS setting at System Settings > Privacy & Security > Local Network. Apps have to be given permission there to access devices on the local network. Maybe Firefox lost that setting after an OS update.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (9)

sites1
sites1 Zadający pytanie

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.

TyDraniu
TyDraniu
  • Top 10 Contributor

Go to about:config and check if dom.security.https_only_mode.upgrade_local = false.

sites1
sites1 Zadający pytanie

It is false. That seems to be the default. Is that what I want?

Paul
Paul
  • Moderator
  • Top 10 Contributor

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

TyDraniu
TyDraniu
  • Top 10 Contributor

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.

sites1
sites1 Zadający pytanie

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?

sites1
sites1 Zadający pytanie

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?

sites1
sites1 Zadający pytanie

Today I went all the way back to Firefox 129.0.1 (12-Aug-2024), using new profile. The behavior is the same. No way to log in to local server or router.

Zmodyfikowany przez sites1 w dniu

sites1
sites1 Zadający pytanie

Wybrane rozwiązanie

This problem turned out to be due to an obscure macOS setting at System Settings > Privacy & Security > Local Network. Apps have to be given permission there to access devices on the local network. Maybe Firefox lost that setting after an OS update.