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

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
Đã giải quyết

firefox doesn't show prompt to allow Local Network Access

q.rotscheid

Last Friday August 21 2026 my Firefox was updated from version 153.0.4 to version 154.0. Ever since then i can't use any of the Azure functions needed to see dead-letters in our service bus explorer. When i try the same in edge or chrome i get a prompt to allow access to local device network. Firefox doesn't show the prompt. In my settings no websites are listed in the Permissions and data list. When i look at the site specific permissions (shield button -> show site information -> permissions) it is set to default prompt. Clearing cookies or accessing through a private window makes no difference. I need to give Azure access to local network otherwise it throws a web socket error whenever i try to peek at any of our service bus messages. Anyone any ideas?

Last Friday August 21 2026 my Firefox was updated from version 153.0.4 to version 154.0. Ever since then i can't use any of the Azure functions needed to see dead-letters in our service bus explorer. When i try the same in edge or chrome i get a prompt to allow access to local device network. Firefox doesn't show the prompt. In my settings no websites are listed in the Permissions and data list. When i look at the site specific permissions (shield button -> show site information -> permissions) it is set to default prompt. Clearing cookies or accessing through a private window makes no difference. I need to give Azure access to local network otherwise it throws a web socket error whenever i try to peek at any of our service bus messages. Anyone any ideas?
Đọc câu trả lời này trong ngữ cảnh

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

in about:config switching "network.lna.websocket.enabled" back from true to false does indeed fix the problem. When set to false i no longer get the websocket error when calling the peek/receive servicebus azure functions.

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

Setting permission to allow on the site directly doesn't work, because it's the domain that the underlying service bus peek function uses that needs the permission.

Would you be willing to file a bug with these details, potentially based on the change in bugzilla.mozilla.org/2042339 …?

Generally this is the preference changed: hg.mozilla.org/integration/autoland/rev/a6d2a53cca50

You can either flip network.lna.websocket.enabled back, or potentially add exclusions to network.lna.skip-domains …?

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

in about:config switching "network.lna.websocket.enabled" back from true to false does indeed fix the problem. When set to false i no longer get the websocket error when calling the peek/receive servicebus azure functions.

In case it's related, I'm linking a fresh bug to potentially follow: bugzilla.mozilla.org/2065861 if the culprit is the same.

Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.