Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Local server won't load

  • 2 trả lời
  • 6 gặp vấn đề này
  • 1001 lượt xem
  • Trả lời mới nhất được viết bởi teferrin

more options

I run a Synology DSM server on my local network. The website page to load locally inside my LAN is along the lines of 127.0.0.1:1001.

MacOSX 15.0.1 FireFox(FF) 132.0 (aarch64)

Previously accessing the DSM via the local IP address worked fine with no problems. Now, following one of the last couple of FF updates, I get an "unable to connect" message.

I also have a domain that routes to my local server and I can still access the DSM via the internet http address through FF. So I know that DSM is running fine and I have verified the settings within DSM.

I can load the DSM via the local IP in both Safari and Chrome. Only FF says it's unable to connect. So that shows that my DSM settings are fine and the page is available and loads in Safari and Chrome via the local IP.

I searched the forum and found similar postings, but not quite the same issue as mine. I deleted the cache & cookies/site data. I ensured the Proxy mode in FF is set to "No Proxy". I do not have any extensions running or themes.

I am at a complete loss at what setting in FF I need to change to restore this functionality.

Thanks, Matt

I run a Synology DSM server on my local network. The website page to load locally inside my LAN is along the lines of 127.0.0.1:1001. MacOSX 15.0.1 FireFox(FF) 132.0 (aarch64) Previously accessing the DSM via the local IP address worked fine with no problems. Now, following one of the last couple of FF updates, I get an "unable to connect" message. I also have a domain that routes to my local server and I can still access the DSM via the internet http address through FF. So I know that DSM is running fine and I have verified the settings within DSM. I can load the DSM via the local IP in both Safari and Chrome. Only FF says it's unable to connect. So that shows that my DSM settings are fine and the page is available and loads in Safari and Chrome via the local IP. I searched the forum and found similar postings, but not quite the same issue as mine. I deleted the cache & cookies/site data. I ensured the Proxy mode in FF is set to "No Proxy". I do not have any extensions running or themes. I am at a complete loss at what setting in FF I need to change to restore this functionality. Thanks, Matt

Giải pháp được chọn

After posting this, I figured out the issue. It's a MacOS configuration issue.

I forgot that MacOS (and iOS) will block application access to local networks, etc.

It took me some time to find the setting, but somehow the FF setting had been turned to off. Perhaps during one of the FF updates or when I updated my MacOS a few weeks ago. Guessing I clicked through some setting and missed it.

To get to that setting, navigate to: Settings > Privacy & Security > Local Network

Once I turned the slide to on, I could access the DSM server via the local IP address again.

Đọc câu trả lời này trong ngữ cảnh 👍 18

Tất cả các câu trả lời (2)

more options

Giải pháp được chọn

After posting this, I figured out the issue. It's a MacOS configuration issue.

I forgot that MacOS (and iOS) will block application access to local networks, etc.

It took me some time to find the setting, but somehow the FF setting had been turned to off. Perhaps during one of the FF updates or when I updated my MacOS a few weeks ago. Guessing I clicked through some setting and missed it.

To get to that setting, navigate to: Settings > Privacy & Security > Local Network

Once I turned the slide to on, I could access the DSM server via the local IP address again.

more options

I had this same problem and it took me a long time to figure out that it was due to a system setting affecting only one application (Firefox). Chrome and wget from within a terminal window worked fine, which of course made me think it must have something to do with FF. Pretty sure I never explicitly turned off FF's access to the local network, at least not though the System Settings menu. So it's a mystery how the setting got changed. Sure wish macOS had a notification setting that would optionally pop-up an alert if a blocked app tried to access the local network as that would have made tracking down the problem trivial.