Fix a 404 Not Found error
A 404 Not Found means the server looked and there’s nothing at that URL. The fix depends on whether it’s a static file or an app route.
Static files
- Check the path and filename — URLs are case-sensitive on Linux
(
Logo.PNG≠logo.png). The folder layout is the URL layout. - Is the file actually there? Confirm in the File Manager. A failed upload or a file left in a subfolder is a common cause.
- Home page 404? You need an
index.html/index.phpin the web root.
Single-page apps (React, Vue, SvelteKit static…)
A hard refresh or direct visit to /dashboard 404s because the server looks for a
file at that path, but the route only exists in the browser. Fix: fall back to
index.html for unknown routes (history-mode fallback). See the SPA notes in
static sites & SPAs.
App routes (WordPress, Laravel, etc.)
- WordPress permalinks 404 → flush permalinks (Settings → Permalinks → Save), and make sure rewrites are enabled for the site.
- Laravel / framework routes 404 → confirm the route exists, the
web root points at
public/, and rewrites send unknown paths to the front controller.
After moving or migrating a site
Broken links post-migration usually mean old absolute URLs or a changed path. For WordPress, run a search-replace of the old domain → new domain — move a WordPress site.
Custom 404 page
Once the real 404s are fixed, a friendly custom 404 page improves the experience
for genuinely missing URLs — add one in your app or as 404.html.
Running OrbixPanel? The File Manager makes it easy to confirm a file is really where the URL expects it. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.