Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Etsi tuesta

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

Unable to load website if any background XHR request is failed

  • 1 vastaus
  • 0 henkilöllä on sama ongelma
  • 1 näyttö
  • Viimeisin kirjoittaja bbalendrakumar

more options

I am using Firefox Developer Edition Version: 110.0b5 (64-bit) on M1 Mac running Ventura 13.1.

I am building an webapp some XHR triggering in background but it is not necessary to run the application (running fine on other browsers). But on Firefox Developer Edition, It shows a error window with the message and stops loading the application.

Firefox can’t establish a connection to the server at localhost:4000.

localhost:4000 is the failing XHR request domain. I have attached the screenshot.

How to ignore the XHR failing errors just like other browsers?

I am using '''Firefox Developer Edition''' Version: 1'''10.0b5 (64-bit)''' on '''M1 Mac''' running '''Ventura 13.1'''. I am building an webapp some XHR triggering in background but it is '''not necessary''' to run the application (running fine on other browsers). But on '''Firefox Developer Edition''', It shows a error window with the message and stops loading the application. '''Firefox can’t establish a connection to the server at localhost:4000.''' ''localhost:4000'' is the failing XHR request domain. I have attached the screenshot. How to ignore the XHR failing errors just like other browsers?
Liitetyt ruutukaappaukset

Valittu ratkaisu

It is resolved. Actually, It's a iFrame, The error appears inside the iframe that looks like an browser alert.

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (1)

more options

Valittu ratkaisu

It is resolved. Actually, It's a iFrame, The error appears inside the iframe that looks like an browser alert.