Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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 réponse
  • 1 a ce problème
  • 5307 vues
  • Dernière réponse par #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?

Modifié le par #367259

Solution choisie

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? :-/

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

#367259
#367259 Auteur de la question
more options

Solution choisie

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? :-/