Managing Custom Error Pages in DirectAdmin

A custom error page is the page visitors see instead of the server's plain message when something goes wrong, such as a missing page (404) or a blocked folder (403). A good one keeps visitors on your site with a link home or a search box. This guide shows how to set up custom error pages on Domain India's DirectAdmin hosting, where it works through files and .htaccess rather than a panel editor.

1. Which error pages are worth customising

Start with the 404 page: real visitors see it most, from old bookmarks, typos and removed pages.

2. How error pages work on Domain India DirectAdmin

We checked our DirectAdmin servers on 23 September 2026:

• The DirectAdmin interface no longer has a Custom Error Pages tool, so older guides that tell you to open it describe a menu you won't find.
• The web server is Apache, and it is already set to use /404.shtml as the "not found" page for every site. If that file exists in your website's folder, visitors see it; if it doesn't, they see Apache's plain default message.
• .htaccess files may set their own error pages with ErrorDocument, so you can add pages for any other code.
• Many older accounts already have a 404.shtml in public_html with a plain "Not Found" message. If yours does, that is the file to edit.

Your website's folder is domains/yourdomain.com/public_html. For a subdomain it is the subdomain's own folder.

3. Create a custom 404 page

A simple, self-contained 404 page:

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Page not found | Your Business</title>
  <style>
    body { font-family: system-ui, sans-serif; max-width: 36rem; margin: 15vh auto; padding: 0 1rem; color: #222; }
    a { color: #0a58ca; }
  </style>
</head>
<body>
  <h1>Sorry, we can't find that page</h1>
  <p>We couldn't find <!--#echo var="REQUEST_URI" --> on this site. It may have moved, or the link may be mistyped.</p>
  <p><a href="/">Go to the home page</a></p>
</body>
</html>

Because the file ends in .shtml, the server fills in the <!--#echo var="REQUEST_URI" --> line with the address the visitor asked for; we tested this on our DirectAdmin servers. Remove that line if you don't want it. Keep styles inside the page, as in the example, and use links that start with /. The error page can be shown at any address on your site, so relative links to images or CSS files often break.

4. Add pages for other error codes with .htaccess

For other codes, create one file per error and point to each with an ErrorDocument line in the .htaccess file in public_html. A tidy way is a folder called errors:

ErrorDocument 403 /errors/403.html
ErrorDocument 404 /errors/404.html
ErrorDocument 500 /errors/500.html
ErrorDocument 503 /errors/503.html

A line in .htaccess overrides the server's default, so if you add ErrorDocument 404, the file you name there is used instead of 404.shtml.

Rules that avoid surprises:

• Use a path that starts with /, not a full https:// address. With a full address, Apache redirects the visitor to that page and the real error code is lost, so search engines see a normal page instead of a 404.
• Edit .htaccess carefully. One typo gives the whole site a 500 error. Keep a copy of the working file before you change it.
• Don't add php_value or php_flag lines. PHP on our servers doesn't run as an Apache module, so those lines cause a 500 error. Change PHP settings from the panel instead.
• Only some Options values are allowed on our DirectAdmin servers: Indexes, IncludesNOEXEC, MultiViews, SymLinksIfOwnerMatch, FollowSymLinks and None. Any other value gives a 500 error.

For more on .htaccess rules, see How can I enable the mod_rewrite module.

5. When your custom page won't appear

To check that your 404 page returns the right status code, not just the right look, run this on your computer:

curl -sI https://yourdomain.com/test-missing-page | head -1

The first line should say 404. If it says 200, search engines will treat every missing address as a real page (a "soft 404"), which hurts how your site is indexed.

For finding the cause of the errors themselves, see Understanding and resolving HTTP status codes in cPanel and DirectAdmin, Troubleshooting 500 Internal Server Error and How to access and analyze logs in DirectAdmin.

6. What makes a good error page

• Say what happened in plain words. "We can't find that page" beats "Error 404".
• Offer a way forward: a link home, your main sections, a search box or a contact link.
• Keep it light. No large images or external scripts; an error page should load even when parts of the site are struggling.
• Show no technical details such as file paths, server names or database messages.

On a cPanel plan the idea is the same, but cPanel still has its own Error Pages tool for editing these pages in the panel.

7. Where Domain India DirectAdmin hosting fits

Everything above works on every Domain India DirectAdmin plan: Apache with .htaccess support, a File Manager, and free Let's Encrypt SSL so your error pages load over HTTPS like the rest of the site. Weekly JetBackup backups let you restore a file if an edit goes wrong.

Frequently asked questions

Ready to set up your error pages? Open your hosting list, click the DirectAdmin button and start with 404.shtml. Looking for hosting? Compare DirectAdmin hosting plans.