404 Rescue · Diagnostics Panel

This page replaced your index.html and loaded successfully.
✅ Your web server is alive — the 404 error likely affects other files, routes, or misconfiguration.

⚙️ Self-check page · JavaScript enabled

📡 Active request environment

Requested URL

-

Pathname

-

Document Root (assumed)

/public_html or htdocs

User Agent

-

🌐 Full address: loading...

ℹ️ The fact you see this page means index.html is being served from the correct directory.
If you were expecting a different page (like /home or /blog) the server might be missing rewrite rules or the file doesn't exist.

🔎 File & resource checker

Test if specific files exist on your server (relative to this folder / domain root).
Enter a relative path e.g. style.css, images/logo.png, js/app.js or /wp-login.php

💡 Click "Check existence" to see HTTP status. 200 = file exists, 404 = missing.

📌 Quick common checks

🛠️ Why "Not Found" & ErrorDocument issue?

The original error shows: "Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."
That usually means your server's custom error page (e.g. ErrorDocument 404 /some-page.html) is also missing or points to an invalid location.

⚠️ Typical root causes:
- No index.html / index.php in the main web folder (document root).
- .htaccess rewrite rules are broken or redirect to a non‑existent resource.
- The requested URL contains a typo, or the file/folder permissions are too restrictive (e.g. 644 for files, 755 for folders).
- Apache/Nginx virtual host points to the wrong directory.
- Case‑sensitivity issue (Linux servers): Index.html ≠ index.html.

✅ Step‑by‑step fixes to try:

Make sure your main index file is named exactly index.html (or index.php if PHP enabled) and located in the document root (often public_html, www, or htdocs).
Check .htaccess (if present): rename it temporarily to .htaccess_backup and reload your site. If the error disappears, the rules are faulty.
Verify file permissions: set folders to 755 and files to 644 (using FTP or cPanel File Manager).
If you moved files recently, ensure the web server points to the correct path. Use the File Checker above to test if /index.html returns 200 (this page itself will be 200).
Check ErrorDocument directive in .htaccess or httpd.conf – it may point to a file that doesn’t exist. Remove or fix the path.
If you're using a framework (React, Vue, Laravel, WordPress) you might need URL rewriting. Try accessing /index.php or a file that does exist (like /robots.txt).

🧪 Manual check using fetch API

You can test individual paths (relative to current domain root), and see exact HTTP status and error details.

← Type a URL path, click button, see real status.

💡 Tip: If /index.html shows 200, but your domain root gave 404 before — then the server default index file was missing. Now it's fixed. If other pages show 404, their actual files are missing / mislinked.

📋 Next actions (recommended)

🔧 contact hosting support

If the file checker shows 404 for everything except this page, the document root might be wrong. Upload a dummy file test.txt and try to access it. Contact support to verify root directory.

📁 Enable directory listing (temporary)

Add Options +Indexes to a temporary .htaccess (if allowed) to see what files exist in your public folder.

⛔ Clear cache & cookies

Sometimes a cached redirect or old 404 page is stuck. Hard refresh (Ctrl+Shift+R) or open incognito.

🔗 Important : After troubleshooting, rename this diagnostic file to something like diagnostic.html and upload your real index.html back. Or keep as backup.