More detail on the new Error page

[Feyd]

Since the last update (Morning of 25/03/26) My default error page has vanished any specific information on the error code... It only comes up with

Looks like there’s a problem with this site

Firefox can't connect to the server at xxxxx.com

What can you do about it?

The site could be temporarily unavailable or too busy. Try again in a few moments.

With the option to "try again". I have to open the network tools and reload the page at which point the error could be gone & I'm left knowing there is an error with my site, but not which one...

Even a little closed by default "more info" drop down, just to show error code 4xx/5xx would be enough for me! (but I'm sure there would be more information needed by others?)

C'mon peeps, I'm already the only one using Firefox in my team. This seems like a footgun for devs 😛 ?

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

[Jon]

@Feyd there's a similar idea here: More detailed error page, firefox 

[Feyd]

Thanks @Jon 

I've Kudos-ed them, but that's a 2 year old idea and the new error pages seems to have reduced the visible diagnostic information.

[DreamingVoid]

A connection issue literally means you can't connect to the server. The server is not responding. There is no HTTP response status code to show you.

[PearlDragon]

@DreamingVoid the problem is that Firefox is giving a misleading message to anything that isn't a 200 OK. 
You can verify this by browsing to https://httpbin.org/status/404
You should get, after successfully connecting to the server, a 404 File Not Found, instead you get "Firefox Developer Edition can’t connect to the server at httpbin.org"
Which is patently untrue

[daroot]

I don't know how to feel about this, displaying the error (401, 404, 500) is as old as the internet, users and developers alike are used to seeing error codes, 404 is culturally known as "not found". Who benefits from this? Because we all see clearly who suffers from this. Weird decision honestly 

[aaprillaman]

@DreamingVoid 

This is the error seen when a DNS lookup fails now.

And here is the error shown for a 404 with no body content.

This 404 error page is fundamentally misleading the user, above and beyond not including the error code because it's saying that it can't connect to the server, which is fundamentally false. It connected to the server and got back a not found response.

This is the stated reason for this change in the release notes.

---

Firefox error pages have a fresh new look, with updated visuals that better match the overall feel of Firefox. The redesigned pages create a more cohesive experience while making it clearer what went wrong.

---

This change fundamentally fails to do what your release notes claim it does.

I support a CMS platform, I frequently find myself troubleshooting issues experienced by my customers and their customers.

A basic screenshot of the error page a user is seeing was incredibly useful when provided.

And now it's not. Even basic troubleshooting now requires a dive into Web Developer Tools, which is a huge ask from the general public. It one less reason to recommend Firefox over Chromium based browsers.

[chezbunch]

Please tell us how to disable this crap and revert to previous meaningful errors. That's the kind of change that makes me realize you don't care about users and make me go the Chrome way.

[SuneK]

This is incredibly stupid. Not showing the respons code when you get one is very misleading. 

[Warpc0il]

Isn't there at least a config option to switch back to meaningful error codes?

This "branding" is all gloss and no substance.

[pb1]

This is idiotic. Having an error code and descriptive message is necessary to troubleshoot. This cutesy "users are idiots" mentality is shortsighted and dumb.