Resolving 404 Errors on Your Website: A Guide for DirectAdmin and cPanel End Users

A 404 Not Found error means the web server was reached, but it has nothing at the address that was requested. The fix is almost always in your own files, links or rewrite rules, so you can solve it from your control panel without server access. This guide walks through the causes in the order to check them, for cPanel and DirectAdmin hosting.

1. What a 404 tells you

The browser reached your server, and the server answered, but no file or route matches the address. That rules out several other problems:

If you see a 403 or 500 instead, see HTTP error 403 Forbidden or troubleshooting 500 Internal Server Error.

2. Check the URL exactly

• Spelling and letter case. Our Linux servers treat About.html and about.html as different files. A link to /Images/logo.png won't find /images/logo.png.
• The file extension. .htm is not .html, and .jpeg is not .jpg.
• Trailing parts. Extra slashes, spaces (shown as %20) or a query string copied wrongly can all miss the page.

Open the URL in a private window to rule out an old bookmark or browser cache.

3. Check the file is in the right folder

Every domain on your account has a document root: the folder the server reads for that domain.

• The main domain's document root is usually public_html.
• Addon domains and subdomains have their own folders. On cPanel, the Domains page shows each one's document root; on DirectAdmin, each domain has its own public_html under domains/yourdomain.com/.

Open the File Manager and check the file is really there, with the exact name. A common mistake is uploading the whole site folder, so the files end up in public_html/mysite/ and the home page is only at yourdomain.com/mysite/. Move the files up one level. See how to use the File Manager.

4. Fix rewrite rules for WordPress and other CMSs

If the home page works but every other page gives 404, the rewrite rules are missing or broken. Content-managed sites such as WordPress, Laravel and most PHP frameworks use .htaccess rules to send "pretty" URLs to one index file.

# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
# END WordPress

If WordPress is installed in a subfolder, RewriteBase and the last rule must include that folder, for example /blog/. mod_rewrite is enabled on our cPanel, DirectAdmin and Webuzo servers, so you don't need to switch it on; see enabling the mod_rewrite module.

5. Redirect pages you moved or deleted

When you rename, move or remove a page, old links and search results still point to the old address. Send them to the best new page with a permanent (301) redirect in .htaccess:

Redirect 301 /old-page.html https://yourdomain.com/new-page/
Redirect 301 /services/web-design https://yourdomain.com/web-design/

For WordPress, a redirect plugin does the same from the dashboard. If a page is gone for good with no replacement, a 404 (or 410 Gone) is the correct answer; don't redirect everything to the home page.

6. Find and fix broken links

A 404 often comes from a link, not from a missing page.

• Google Search Console lists pages Google found as "Not found (404)" under the Pages report, and shows where the link came from.
• A link checker such as the W3C Link Checker scans your pages and lists every broken link.
• Inside WordPress, search your posts for the old address and update the links.

Fix links on your own site first; you control those. For links from other sites, use a 301 redirect.

7. Read the logs

Your control panel keeps two logs that help:

• The access log records requests with their status codes. Search it for 404 to see which addresses fail, how often, and which page sent the visitor (the referrer).
• The error log records .htaccess mistakes, PHP errors and rewrite problems that can sit behind a 404 on a CMS page.

On cPanel, the error log is under Metrics › Errors and the access logs under Metrics › Raw Access. On DirectAdmin, each domain has its own access and error logs. See reviewing error logs in cPanel and DirectAdmin.

8. Show a helpful 404 page

Visitors will still hit a wrong address sometimes. A custom 404 page with a search box and links to your main pages keeps them on your site. WordPress themes include one. For a static site, create 404.html and add this line to .htaccess:

ErrorDocument 404 /404.html

Make sure the custom page still returns the 404 status code, so search engines don't index it as a real page.

9. When to contact support

If the file is in the right place, the URL is correct and the log doesn't explain it, open a ticket with the full URL, the time you saw the error and what you already checked. Our support team is on 24/7 live chat, and tickets get a first response within 15 minutes, though resolution can take longer depending on the issue.

If you're moving to new hosting, our plans include cPanel with the File Manager, error logs and .htaccess support described here.

The price on the card is a Domain India list price and excludes 18% GST.

Frequently asked questions

Ready to fix it? Open My Hosting to reach your control panel and File Manager, or open a ticket if the 404 won't go away.