Diagnose the wrong website or a 404
Distinguish DNS, virtual-host routing and application content.
Before you begin
Exact hostname and intended document root.
Use the controls offered by your installed version and account permissions. This guide describes the workflow; it does not grant additional access.
Follow the steps
- Confirm DNS resolves to the intended server.
- Inspect domain ownership and root in EzePanel.
- Check the expected index or application entry file exists.
- Review relevant routing and application errors with the provider.
- Retest the same hostname over HTTP and HTTPS after a targeted correction.
Check the result
The URL serves the expected application.
If something goes wrong
Do not copy files into the global server web root. An application 404 differs from a refused TCP connection.
Prepare useful details for support