Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

mikey8811

macrumors regular
Original poster
Mar 23, 2019
123
21
Hi

Since I updated to Sequoia I have had problems with Firefox connecting to local sites on my network.

I cannot reach my router admin page at 192.168.0.1 or other such addresses. Initially it happened intermittently. It didn't work at the start but would work after some time.

Now, it just doesn't work.

No issues with Safari.

Anybody else have this problem and how did you fix this?

Thanks
 
  • Like
Reactions: brewmonkey

mikey8811

macrumors regular
Original poster
Mar 23, 2019
123
21
As per screen capture

Firefox Error.png
 

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,489
16,217
California
If I just enter 192.168.1.1 in FF it redirects to the URL I posted earlier. I wonder if you have some FF security setting configured differently than I do.
 

mikey8811

macrumors regular
Original poster
Mar 23, 2019
123
21
If I just enter 192.168.1.1 in FF it redirects to the URL I posted earlier. I wonder if you have some FF security setting configured differently than I do.
I don't know. I didn't touch the settings and it worked fine before Sequoia.
 

JP-1

macrumors newbie
Oct 9, 2024
3
3
Same Here. I upgraded to Sequoia last night, and now Firefox is now unable to connect to any websites on my local network. I can only access sites on the internet. Safari Browser is able to access local sites OK, and all other local network services are fine. Only Firefox seems to be affected.
 

mikey8811

macrumors regular
Original poster
Mar 23, 2019
123
21
Same Here. I upgraded to Sequoia last night, and now Firefox is now unable to connect to any websites on my local network. I can only access sites on the internet. Safari Browser is able to access local sites OK, and all other local network services are fine. Only Firefox seems to be affected.
I updated a day after Sequoia came out so it hasn't been working for a while for me. I hope someone fixes it either on the Apple side or the Mozilla one.
 

Grumpus

macrumors 6502
Jan 17, 2021
387
222
Firefox 131.0.2 was pushed out today. Might not hurt to update to see if the problem goes away.
 

JP-1

macrumors newbie
Oct 9, 2024
3
3
My Firefox is already updated to 131.0.2, Wifi disabled, Static Ethernet configuration, Firewall disabled. I have at least a couple dozen systems on my local network that can no longer be accessed via Firefox.

After the OS upgrade completed I was prompted to "allow Firefox to find devices on local networks?" "this will allow the app to discover, connect to, and collect data from devices on your local networks"

I clicked don't allow, as it sounded un-neccesary to "collect data" on my devices. I am unable to find any security settings in Firefox or OS X to adjust this option to see if this is why the web devices are no longer accessible.
 

IanRL

macrumors newbie
Aug 6, 2015
4
0
I have the same problem, but I don't see firefox in Privacy & Security / Local Network. Is there a way to add it?
 

mikey8811

macrumors regular
Original poster
Mar 23, 2019
123
21
Ah, I found it,

OS X System settings, Privacy and Security, Local Network, flip the slider on for Firefox. I am back in business!
I have the slider already turned on from the start. No effect. I still have the problem
 

IanRL

macrumors newbie
Aug 6, 2015
4
0
I have the same problem, but I don't see firefox in Privacy & Security / Local Network. Is there a way to add it?
I've since found that MS Edge has the same issue, but it does have an entry in the Local Network app list, and it's slider is "on". Safari works fine, although like Firefox, it doesn't have an entry in the Local Network app list. I'm a little confused by this...
 

4nthony

macrumors newbie
Nov 16, 2020
24
5
As I was typing this, I noticed @Grumpus reply above. I turned off "Private Wi-Fi Address" and access to 192.168.1.1 was allowed. Original message below. Cheers.


Monosnap_2024-10-27_11-10-01.png



On my Sequoia system, both Chrome, Safari, and curl (terminal) are unable to connect to 192.168.1.1.

At first I thought it was Little Snitch, but I've disabled that completely. I've also checked the Privacy & Security settings and have enabled the sliders for Local Network Access. When Local Network is disabled, Chrome reports that it is unreachable. When enabled, Chrome reports a time out.

I can ping 192.168.1.1. Traceroute also returns.

I can open other IPs in the range (.2, .3, .4, etc) but .1 never resolves. On may iMac running Ventura, .1 works fine.

All user accounts on this machine have the same symptoms. I can't figure out what is blocking the requests. I'm stumped.
 

brewmonkey

macrumors regular
Feb 17, 2016
215
141
I just got an M4 Mini which is the first Mac I've had that can run Sequoia. It did this same thing to me. I searched around and found that you have to enable a setting to allow Firefox to access local network resources. Settings -> Privacy & Security -> Local Network. Checking Firefox in that list allows it access to local network resources but I've found it's flaky and seems to "forget" the setting and block access randomly (even though the setting remains enabled). Toggling it off and on seems to restore local access.

Quite a bumble on Apple's part implementing a new mechanism for security that does not work reliably.
 
  • Like
Reactions: Te0SX

Alameda

macrumors 65816
Jun 22, 2012
1,296
888
As I was typing this, I noticed @Grumpus reply above. I turned off "Private Wi-Fi Address" and access to 192.168.1.1 was allowed. Original message below. Cheers.


Monosnap_2024-10-27_11-10-01.png



On my Sequoia system, both Chrome, Safari, and curl (terminal) are unable to connect to 192.168.1.1.

At first I thought it was Little Snitch, but I've disabled that completely. I've also checked the Privacy & Security settings and have enabled the sliders for Local Network Access. When Local Network is disabled, Chrome reports that it is unreachable. When enabled, Chrome reports a time out.

I can ping 192.168.1.1. Traceroute also returns.

I can open other IPs in the range (.2, .3, .4, etc) but .1 never resolves. On may iMac running Ventura, .1 works fine.

All user accounts on this machine have the same symptoms. I can't figure out what is blocking the requests. I'm stumped.
On mine, Private Wi-Fi address is set to "Fixed" and I can still access local network addresses via Firefox, so try that because it can reduce tracking.
 

Te0SX

macrumors regular
Jul 29, 2014
134
219
As every time for the past 3-4 years, I'll wait for more stable updates before I upgrade from Sonoma. Maybe at .4 again. I can't be bothered with these stuff every time. So see you in some months.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.