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:
[NGINX]$scheme://$server_name/?error=$status&return=$request_uri
Let's breakdown the URL
| Type | Breakdown |
| $scheme://$server_name |
This will translate to the URL to the domain that the servers gets the request from. i.e. https://organizr.app |
| ?error=$status |
This will set the correct Status code for the error page |
| &return=$request_uri | OPTIONAL: This will let Organizr know to redirect the user once they have logged in |
You may set custom ones with predefined URLs
https://organizr.app/?error=401&return=https://organizr.app
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.
# for subdomain, replace $server_name with the domain organizr is on
error_page 401 $scheme://$server_name/?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/?error=$status; # Responds with the errorpage for the errorcodes listedPlease see note about Subdomains from above example
For Subdomain's, replace $server_name with the domain organizr is on, i.e. organizr.app
error_page 401 $scheme://organizr.app/?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://organizr.app/?error=$status; # Responds with the errorpage for the errorcodes listed
No Comments