How to Manage Website Error Pages

Overview

Sometimes a visitor may request a page that doesn't exist, access something they aren't permitted to access, or encounter an unexpected problem while your website is loading.

When this happens, the web server can display an error page.

Common examples include:

• 404 Not Found — the requested page or file could not be found.

• 403 Forbidden — access to the requested resource is not permitted.

• 500 Internal Server Error — the server encountered an unexpected problem while processing the request.

• 401 Unauthorized — the requested resource requires authentication.

Have Freedom Hosting provides tools in cPanel that can allow you to customize certain website error pages.

Why Customize Error Pages?

The default server error pages are functional, but they may not match the design of your website.

A customized error page can:

• Keep your branding consistent

• Help visitors understand what happened

• Provide useful navigation

• Link visitors back to your homepage

• Provide contact information

• Reduce confusion when a page is unavailable

For example, instead of showing a generic 404 message, you could display:

We couldn't find that page. Try returning to the homepage or searching our website.

Where Do I Manage Error Pages?

If the feature is available on your hosting account, you can access it through:

cPanel → Advanced → Error Pages

The exact location and availability may vary depending on your hosting plan and cPanel configuration.

If you don't see the Error Pages feature, contact Have Freedom Hosting Support.

Common Error Codes

404 — Not Found

A 404 error means the requested resource could not be found.

For example, a visitor may attempt to access:

https://example.com/old-page

when that page no longer exists.

A 404 error can also happen because:

• A page was deleted

• A URL was entered incorrectly

• A link is outdated

• A file was moved

• A website was recently migrated

• A WordPress permalink is misconfigured

A 404 does not necessarily mean your entire website is broken.

403 — Forbidden

A 403 error means access to the requested resource was denied.

Possible causes include:

• File or directory permissions

• Access rules

• .htaccess configuration

• Security settings

• Directory restrictions

If you unexpectedly begin receiving 403 errors, investigate the underlying cause rather than simply replacing the error page.

500 — Internal Server Error

A 500 error means the server encountered an unexpected problem while processing the request.

Possible causes include:

• PHP errors

• Incorrect .htaccess rules

• Application problems

• Plugin or theme problems

• Incorrect configuration

• Permission problems

• Server-side issues

A custom 500 page can make the visitor experience better, but it does not fix the underlying problem.

401 — Unauthorized

A 401 error generally means the requested resource requires authentication or the supplied authentication credentials were not accepted.

This may be intentional if your website uses protected areas.

Creating a Custom Error Page

To create an error page through cPanel:

1. Log in to cPanel.

2. Open Error Pages.

3. Select the domain you want to manage.

4. Select the error code you want to customize.

5. Enter your custom content.

6. Save the page.

7. Test the result.

The exact options available may vary depending on your cPanel configuration.

Keep Error Pages Simple

An error page should help visitors recover from the problem.

Useful information may include:

• Your website name

• A short explanation

• A link to your homepage

• A link to important sections

• A search option

• Contact information, when appropriate

Avoid filling an error page with technical information that ordinary visitors won't understand.

Example 404 Page

A simple 404 page might say:

Page Not Found

Sorry, we couldn't find the page you were looking for.

The page may have been moved, deleted, or the address may have been entered incorrectly.

Please return to our homepage or use the site's navigation to find what you're looking for.

You can customize the wording to match your website.

Example 500 Page

A 500 page should avoid blaming the visitor.

For example:

Something Went Wrong

We're sorry, but the website encountered an unexpected problem.

Please try again in a few moments.

If the problem continues, please contact us for assistance.

Keep technical troubleshooting information out of the visitor-facing message unless it is genuinely useful.

Don't Use Error Pages to Hide Problems

A customized error page improves the visitor experience, but it should not be used to hide a recurring website problem.

For example, if your homepage suddenly produces a 500 error, replacing the error page doesn't fix the homepage.

Instead:

1. Identify what changed.

2. Check your application.

3. Check recent plugin or theme changes.

4. Check .htaccess.

5. Review available error information.

6. Contact support if necessary.

Testing Your Error Pages

After creating or changing an error page, test it.

For a 404 page, you can visit a URL that doesn't exist:

https://example.com/this-page-does-not-exist

You should see your custom 404 page.

Be careful when testing other error codes. You should not intentionally break a working website simply to generate an error.

Error Pages and WordPress

WordPress can handle some errors through its own themes and templates.

For example, many WordPress themes include a 404.php template that controls the appearance of a WordPress 404 page.

This means your website may have both:

• A server-level error page

• A WordPress/application-level error page

Which one visitors see depends on how the request is handled.

If you're using WordPress and want your 404 page to match the rest of your website, check your active theme before changing the server-level error page.

Error Pages and .htaccess

Your .htaccess file can also contain rules affecting error handling.

For example, a website may use rules to redirect certain errors to specific pages.

If you recently changed .htaccess and your error pages stopped working correctly, review those changes.

Always keep a backup before making changes to .htaccess.

Error Pages and Redirects Are Different

An error page and a redirect serve different purposes.

A 404 page tells a visitor that a requested page could not be found.

A redirect sends a visitor somewhere else.

For example:

Old URL
   ↓
301 Redirect
   ↓
New URL

If a page has permanently moved, a redirect is generally more useful than simply displaying a 404 page.

Common Problems

My Custom Error Page Isn't Showing

Check:

• That you selected the correct domain.

• That the error page was saved.

• That the requested error is actually being generated.

• Whether WordPress or another application handles the error instead.

• Whether .htaccess contains custom error rules.

• Whether your browser or a caching system is displaying an older response.

My Website Shows a 404 Instead of the Page I Expected

A 404 may indicate that:

• The URL is incorrect.

• The page was deleted.

• The file was moved.

• A WordPress permalink is incorrect.

• DNS or domain configuration is pointing somewhere unexpected.

• Your website application isn't handling the request correctly.

Don't automatically assume the custom error page is the problem.

My Website Shows a 500 Error

A 500 error generally requires troubleshooting rather than simply changing the error page.

Check recent changes to:

• .htaccess

• PHP settings

• Plugins

• Themes

• Website code

• Application configuration

If you cannot determine the cause, contact Have Freedom Hosting Support.

Keep Your Error Pages Up to Date

If your website design changes, remember to update your error pages as well.

A customized error page should still:

• Match your website

• Work on mobile devices

• Provide useful navigation

• Use working links

• Avoid unnecessary technical information

Test your error page periodically to make sure it still works as expected.

When to Contact Have Freedom Hosting

Contact Have Freedom Hosting Support if:

• Error pages suddenly stop working.

• Your website begins returning unexpected 403 or 500 errors.

• You believe an error is caused by the hosting environment.

• You cannot determine why a page is returning an error.

• A website-wide problem occurs after a cPanel configuration change.

When contacting support, include:

• Your domain

• The exact URL affected

• The error code

• The exact message displayed

• When the problem started

• Any changes made immediately beforehand

Screenshots can also be useful.

Never include passwords or other sensitive credentials in a support ticket.

Need Help?

Custom error pages can make your website look much more professional when something goes wrong, but they don't replace troubleshooting the underlying issue.

If you're seeing an unexpected error across your website or aren't sure whether the problem is with your website, cPanel configuration, or hosting environment, Have Freedom Hosting Support can help you determine the next step.