JSOPanel Get started
Help Center › Website Owners › Writing your own error pages

Writing your own error pages

Replace the plain default 404, 403, or server-error page with your own, for any real HTTP status code.

By default, a visitor who hits an error (a missing page, a forbidden folder, a server error) sees a plain page the web server shows itself. Web Protection lets you write your own for any real HTTP status code, with tags that fill in details about the visitor and the request when the page is actually shown.

Turning it on and writing a page

  1. Click Domains & SSL in the sidebar, find the domain, and click Manage.
  2. Open the Domain tab and find Web protection.
  3. Tick Use this site's own error pages and click Save protection - without this on, nothing you write below is used.
  4. Under Error pages, five common codes are shown first (400, 401, 403, 404, 500); click Show all HTTP error codes to see every other real one. Click any code to open it.
  5. Write the page's content. To insert a tag that fills in with a real value when a visitor sees the page, place the cursor where you want it and click one of: Referring URL, Visitor's IP address, Requested URL, Server name, Visitor's browser, or Redirect status code.
  6. Click Save.

A code you haven't written anything for simply falls back to the standard page, so you only ever need to write the ones you actually care about. A code that does have its own page shows highlighted in the list, so you can see at a glance what's already customised.

Removing a page

Open the code and click Remove, use the standard page (or simply clear the text and click Save) to go back to the default for that one status code.

Note: the tags above are filled in by the web server itself, so they work correctly on nginx and Apache. OpenLiteSpeed does not support them - a page saved there shows your text exactly as written, with the literal tag text left unreplaced rather than a real value.