If you want your site's visitors to see custom notifications when an error occurs, you can create your own error documents.

Which errors can I intercept?

You can use a document to intercept the following errors:

  • 400
  • 401
  • 403
  • 404
  • 429
  • 4xx -> Check "How do generic error documents work" below
  • 500
  • 502
  • 503
  • 504
  • 5xx -> Check¬†"How do generic error documents work" below

What should I name these documents?

The files you put online should be in HTML-format, and they should carry the name of the specific error #. For example:




What should the file contain?

The contents of the file will be loaded as HTML. You can simply choose to only use text. You can also change the layout like you would with a regular page. CSS is also allowed. You cannot use PHP, however. We strongly advise against using external resources. Are you using images? Make sure they are encoded into the document - do not use external images.

Where should I place the files?

The files have to be placed in the sFTP root, in the 'error_pages' folder. For example:



If you are making a page for a multisite or bilingual site, you can place it into the subdirectory containing the site name. For example:



How do generic error documents work?

When you only want to use one generic error message for every error, you can make a file for the 4xx range errors and 5xx range errors respectively. Unless a more specific error document exists, these generic error documents will be used. They can be placed in the same way, for example:





In this case the 4xx.html will be used for all 4xx range errors, EXCEPT when a 404 error occurs - those will use 404.html.

Do you still have questions regarding the use of custom error documents? Please contact our support crew.