Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
404 pages are not served by addons-frontend
See original GitHub issueDescribe the problem and steps to reproduce it:
- Clear all cookies
- Type in something like https://addons.mozilla.org/nope which redirects to https://addons.mozilla.org/en-US/firefox/nope
What happened?
The 404 is served from addons-server:
What did you expect to happen?
The 404 should be served from addons-frontend. Example:
Anything else we should know?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
How to Fix WordPress 404 Not Found Error [8 Easy Solutions]
How to Fix 404 Error on WordPress (8 Troubleshooting Solutions) · 1. Clear Browser History & Cookies · 2. Set Up Your Permalink...
Read more >How to Fix Error 404 Not Found on Your WordPress Site - Kinsta
All you need to do is go to Settings → Permalinks and click Save Changes (you don't need to make any changes –...
Read more >How to Fix 404 Page or Page Not Found Error Messages
If you are getting a 404 page when you try to navigate to a certain page, or get a 'Page Not Found' error,...
Read more >404 pages for articles as of plugin version 1.3.3 - WordPress.org
2) I see a 404 page whenever I go to the article pages. The slugs are not changed, but for some reason the...
Read more >How to Fix WordPress Posts Returning 404 Error - WPBeginner
Usually in this scenario a user can access their WordPress admin area, their blog's main page, but when accessing a single posts they...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I don’t think there’s much we can do about this one without a big change to how we use the explicit routing.
It will likely get easier once there’s nothing that needs to fall through to the old site. At that point we might be able to control it by just the cookie.
We haven’t run for a good while into 404 errors served by the legacy site, so this issue can be marked as verified fixed.