Error Pages¶
Error Pages let you define your own custom pages for HTTP error status codes (e.g. 404 Not Found) — instead of Nginx's default error page.
Overview¶
The table shows all configured error pages:
| Column | Description |
|---|---|
| Status Code | HTTP status code the page applies to |
| Path | Path to the document, relative to the website's document root |
| Website / Domain | Website the error page applies to |
| Active | Toggle to enable/disable without deleting the entry |
| Created | Creation date |
The table can be filtered by status code and supports sorting and search.
Creating an Error Page¶
- Click Create error page
- Fill in the form:
| Field | Required | Description |
|---|---|---|
| Website | Yes | The website the error page should apply to |
| Status Code | Yes | One of 403 Forbidden, 404 Not Found, 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable |
| Document Path | Yes | Path relative to the document root, e.g. /errors/404.html |
- Click Create
The file must exist
The given path is not created automatically — upload the error page file to your web directory beforehand via the File Manager or FTP.
Editing an Error Page¶
Click the Edit icon to change the document path of an existing error page. Website and status code cannot be changed after creation — delete the entry instead and create it again with the desired status code.
Enabling / Disabling an Error Page¶
The Active toggle in the table lets you temporarily disable an error page without deleting it — Nginx then serves the default error page again.
Deleting an Error Page¶
- Click the Delete icon
- Confirm the deletion
The stored file itself is left untouched — only the mapping in enconf is removed.