We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Thread ini telah diarkib. Sila tanya soalan baru jika anda perlu bantuan.

Firefox can’t establish a connection to the server at ws://127.0.0.1 (plugin or setting is causing this, how to discover exact cause?)

  • 1 balasan
  • 1 ada masalah ini
  • 1 paparan
  • Balasan terakhir oleh #367259

#367259
#367259
more options

Hello, Firefox 91.0.2 shows in dev. console: Firefox can’t establish a connection to the server at ws://127.0.0.1

The Private browsing window has the issue too, but i am unsure if it really disable all extensions.

When i use different Firefox profile, then the localhost site i am trying to load is loaded without that error. So how to discover please which FIrefox profile setting is preventing the loading please?

Hello, Firefox 91.0.2 shows in dev. console: Firefox can’t establish a connection to the server at ws://127.0.0.1 The Private browsing window has the issue too, but i am unsure if it really disable all extensions. When i use different Firefox profile, then the localhost site i am trying to load is loaded without that error. So how to discover please which FIrefox profile setting is preventing the loading please?

Diubah oleh #367259

Penyelesaian terpilih

Tried: FF hamburger menu, Help, Troubleshoot mode... it started working in this no-extensions mode, and after restart to normal mode it is still working. So the workaround was to restart Firefox? :-/

Baca jawapan ini dalam konteks 👍 0

All Replies (1)

#367259
#367259 Pemilik Soalan
more options

Penyelesaian Terpilih

Tried: FF hamburger menu, Help, Troubleshoot mode... it started working in this no-extensions mode, and after restart to normal mode it is still working. So the workaround was to restart Firefox? :-/