A 404 response means the server could not find the requested resource. A page can load while one image, stylesheet, script, or API route fails, so the first task is to identify the exact missing address.
Step-by-step solution
- Open the browser’s developer tools, select Network, and reload the page. Select the request marked 404 and copy its URL.
- If you are a visitor, check the page address and report the broken link to the owner. Clearing your computer or reinstalling the browser cannot restore a missing server file.
- If you own the site, compare the requested path with the deployed file. Check spelling, capitalization, extension, and whether the file was included in the deployment.
- For an app hosted below a subdirectory, inspect its asset base path. A request to /assets/file.js may point to the wrong location when the app lives under /tools/.
- For an API, check the route and HTTP method against the server configuration. For a moved page, restore it or create a redirect to its genuine replacement.
How to check the fix
Reload and inspect that same request. It should return the intended content with a successful status, not an HTML error page disguised as a script.
Before you try other fixes
A missing favicon is different from a missing application bundle. Fix requests that break functionality first.
