When an uploaded static website returns 404, compare the requested URL with the files in the configured document root. An upload can succeed while placing the website one directory too deep. Start with one known file and make its location unambiguous.
Separate the homepage from an inner route
Try the explicit homepage file, such as /index.html, as well as the domain root. If the file works but the root does not, inspect the configured default document. If both fail, confirm the domain points to the intended website and that its document root contains the release you uploaded.
For an inner route, inspect the generated output. A route may correspond to a file such as services.html or a directory containing index.html. A single-page application can require a fallback rule, while a multi-page export should have the corresponding generated page. Identify the deployment mode before adding rewrites.
Compare the exact path
- Check for an extra export or dist directory above the actual homepage.
- Compare filename spelling, extension and letter case with the URL.
- Confirm that referenced scripts and styles use the intended base path.
- Open one inner page directly in a new tab and refresh it.
- Use the browser network panel to distinguish the document response from an asset failure.
Avoid sending every missing URL to a successful homepage response just to hide the error. That can make genuinely missing pages and broken assets harder to diagnose.
Give support a reproducible example
Record the exact failing URL, expected file location, response status and upload time. A screenshot of the folder structure can help if it excludes private files. If the root page works, include that successful URL too; the difference often reveals whether the problem is routing or file placement.
The portable two-page example linked below is a useful control: if its explicit files work in the same directory, compare your export structure and path rules with that known layout.