Custom Error Pages


Organizr comes with integrated error pages, they have to be configured in the webserver.

It accepts most error codes, and can do a redirect when the user has acknowledged the error.


The full Syntax for the error page is:


URL Breakdown




This will translate to the URL to the domain that the servers gets the request from. i.e.


Path to the error page


This will set the correct Status code for the error page

HTTP Error Code (Status Codes)


OPTIONAL: This will let Organizr know to redirect the user once they have logged in

You may set custom ones with predefined URLs

To get error pages to work with a reverse proxies, you may need to tell the webserver to intercept the errors from the service.

In NGINX the way to do this is with proxy_intercept_errors on;

This can break some services (like plex), add proxy_intercept_errors off; to the location if that is the case.

NGINX Example for Proxies

# This is using nginx's built-in variables, should be copy-paste for most setups.
error_page 401 $scheme://$server_name/api/v2/organizr/error/$status?return=$request_uri; # We only want the Unauthorized code to redirect back to the loginpage

error_page 400 402 403 404 405 408 500 502 503 504  $scheme://$server_name/api/v2/organizr/error/$status; # Responds with the errorpage for the errorcodes listed

Organizr Reverse Proxy

If you have Organizr Reversed Proxied, which we are sure you do. You need to add an additional block for the API so it doesn't overwrite the errors for it.

location /api {
    include /config/nginx/proxy.conf; # Replace with any proxy config options
    proxy_pass http://organizr-ip:organizr-port;
    proxy_intercept_errors off; # This is the important part

Last updated