Error Pages ​
URL: /client/error-page - in the sidebar under Domains.
Overview ​
The Error Pages section allows you to customize HTML content displayed when visitors encounter errors like 404 (Not Found) or 500 (Server Error) on your domains. Create branded error page mappings to improve user experience during failures.
Requests to missing .php files
A custom 404 page is served for requests to non-existent .php files as well, not only for missing static files. A visitor who follows a stale link to a script that no longer exists sees your branded page instead of the web server's default one.
Interface Elements ​
Primary Controls ​
- Add Error Page button - Create new custom error page mapping
- Group by dropdown - Organize by (none), Domain, or Error page
- Group direction - Sort ascending or descending
- Search bar - Find specific domains or error codes
- Toggle columns - Show or hide Domain and Updated columns
Current Error Page Mappings ​
Table displaying all configured error pages. Select a domain and error code, then customize its HTML content and save.
Empty State ​
Display message: "No Error Pages" / "You have not created any error pages yet."
This indicates no custom error pages have been configured for your domains.
Workflow ​
- Click Add Error Page to start creating a mapping
- Select a domain from the dropdown
- Choose an error code (e.g., 404, 500)
- Customize the HTML content in the editor
- Save the configuration
Adding an Error Page ​
The "Create or Update Error Page" form allows you to customize HTML content for specific error codes on your domains. Complete the following fields:
- Applied Domain (dropdown, required) - Select which domain the error page applies to
- Error Page (dropdown, required) - Select the error code to customize (400, 401, 403, 404, 500, etc.)
- Select Tag to Insert (dropdown) - Insert template tags to customize the HTML content
- Content (rich text editor) - Customize the HTML content for the error page. A formatting toolbar is provided to help with HTML customization
After configuring your error page, click "Create" to save it or "Cancel" to exit the form.
When a change is refused ​
Since panel 1.9.3, creating, editing, or deleting an error page first checks where the domain's website folder, its .htaccess file, and the error page file in it really lead. If the website folder, a folder above it, or one of these files has been replaced with a symbolic link that leads outside your home directory, the change is refused and nothing is stored or written:
The folder this change writes to, or a file in it, leads outside your hosting account, for example through a symbolic link. Nothing was changed.
Replace the link with a real folder or file, or point it inside your own home directory, then try again. A link that stays inside your home directory is accepted, also when it points outside the website folder.
If the panel cannot complete this check because the server agent does not answer, the change is refused with "Check that the agent is running, then try again." and nothing is changed. If the message persists, contact your hosting provider.
Over the API ​
Since panel 1.9.4, the client REST API manages a domain's custom error pages by HTTP status:
| Method and path | What it does |
|---|---|
GET /api/client/domains/{domain_id}/error-pages | List the domain's custom error pages. |
PUT /api/client/domains/{domain_id}/error-pages/{code} | Set the page for one status, like Add Error Page or Edit. It creates the page (201) or replaces its content (200), and takes only content. |
DELETE /api/client/domains/{domain_id}/error-pages/{code} | Remove the page for one status. |
A page saved from this page is found by its status too, so the API updates it instead of adding a second one. When the change is stored but the web server rules cannot be rebuilt, the answer carries status: partial with the reason and the next step, as When a change is refused describes for this page. The endpoints need this page's feature in your hosting plan; see API Keys.