Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

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.

All Replies (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 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/