Avatar for Username

Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

How can I force a direct IP connection (that used to work)?

  • 3 відповіді
  • 1 має цю проблему
  • 7 переглядів
  • Остання відповідь від cor-el

ramosel
ramosel
more options

Currently running Firefox 65.0.1 (64bit) under windows 10. I have several Linksys e4200s running DD-wrt for APs behind my pfSense firewall. With the new versions of Firefox, the connections are being rejected when accessing them via direct IP. I know the IPs are good, I know they are valid, I know they are working. I can and do access them via IE or Chrome under windows, Safari under iOS and Chromium under Raspian. I used to be able to access them via Firefox. But now when I input their direct local IP, it attempts to force an https connection and I get this:

Unable to connect

Firefox can’t establish a connection to the server at 192.168.1.2. 

   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.

Is there some command line trick to force Firefox to connect to a local network IP?

I do appreciate your attempts at security but you are breaking things that don't need to be fixed! Please let me know if you need more info. Thanks in advance for any help.

Currently running Firefox 65.0.1 (64bit) under windows 10. I have several Linksys e4200s running DD-wrt for APs behind my pfSense firewall. With the new versions of Firefox, the connections are being rejected when accessing them via direct IP. I know the IPs are good, I know they are valid, I know they are working. I can and do access them via IE or Chrome under windows, Safari under iOS and Chromium under Raspian. I used to be able to access them via Firefox. But now when I input their direct local IP, it attempts to force an https connection and I get this: Unable to connect Firefox can’t establish a connection to the server at 192.168.1.2. 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. Is there some command line trick to force Firefox to connect to a local network IP? I do appreciate your attempts at security but you are breaking things that don't need to be fixed! Please let me know if you need more info. Thanks in advance for any help.

Усі відповіді (3)

WestEnd
WestEnd
more options

That sounds like a router issue if the browser can't connect to 192.168.1.1 what does that do?

ramosel
ramosel Власник питання
more options

I'm not having issues getting devices to connect to the APs, I am having issues with Firefox accessing the APs for configuration and maintenance. If I use IE, I can access the AP's webpage If I use Safari on an iOS device, I can access the AP's webpage If I use Chromium under Raspian, I can access the AP's webpage

ONLY when I use Firefox can I not access the APs. Up until a few versions ago, Firefox worked fine too.

for a while you could use a trailing "/" and get it to work, but now even that does not work (ie 192.168.1.3/).

But, I have a backup router so I put that online and not only do the connections fail to the APs but I can't even get to the backup router's webpage. Yes it's working, I'm sending this through that router.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Can these IPs be resolved to an URL because Firefox treats some specific domain as HTTPS only because they are part of the HSTS preload list?

Try to rename/remove SiteSecurityServiceState.txt in the Firefox profile folder with Firefox closed.

Clear the Cache and remove the Cookies from websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).

"Remove the Cookies" from websites that cause problems:

  • Options/Preferences -> Privacy & Security
    Cookies and Site Data -> Manage Data

"Clear the Cache":

  • Options/Preferences -> Privacy & Security
    Cookies and Site Data -> Clear Data -> Cached Web Content: Clear

You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.