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!

Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Cannot access *.localhost

Carlos Martínez
Carlos Martínez
more options

Since Firefox 89 (maybe one or two releases before) *.localhost sites are not accessible, but those sites are available through other browsers or tools (Postman, Chrome, and Edge). Localhost is an Nginx server mounted on WSL2, so it’s IP does not correspond to 127.0.0.1 which is what Firefox thinks (about:networking#dnslookuptool).

There is no Proxy enabled. I also deleted the site settings on Firefox, disabled IPv6 and prefetch with no result.

Since Firefox 89 (maybe one or two releases before) *.localhost sites are not accessible, but those sites are available through other browsers or tools (Postman, Chrome, and Edge). Localhost is an Nginx server mounted on WSL2, so it’s IP does not correspond to 127.0.0.1 which is what Firefox thinks (about:networking#dnslookuptool). There is no Proxy enabled. I also deleted the site settings on Firefox, disabled IPv6 and prefetch with no result.

Alle antwoorden (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hi Carlos, I'm not completely clear on what *.localhost means. You are using .localhost as a top level domain on your network?

If you have a lot of bandwidth and some free time, you could run a Mozregression to identify the specific patch that causes this changed behavior (for example, choose release 86 as your last known good release and 89 as your first known bad release).

More info: https://mozilla.github.io/mozregression/