Error responses

To avoid giving information away about your server, IPP responds with a limited set of HTTP status codes:

Code	Reason
503	Healthcheck failed: Immich is not accessible. Only on /share/healthcheck (and the older /healthcheck).
401	Invalid password provided for a password-protected share link.
204	No upload service at /upload/healthcheck. The gallery checks this path before showing the "Add photos" button; see uploadUrl.
404	All other invalid requests, e.g. album doesn't exist, share link is expired, non-existing file.

Instead of sending the 404 code, you can customise that response by changing the configuration option for customInvalidResponse.

Possible options are:

Option	Data type	Example	Action
HTTP status code	integer	404	Sends an HTTP status code.
Redirect URL	string	"https://example.com"	Redirects to another website.
null	null	null	Drops the connection without responding.
false	boolean	false	Responds with the default status code.

If you want to send a custom 404 page, you would do that with either of the below options - using a custom function, or through your reverse proxy.

Custom function

You can also write your own function. Take a copy of /app/dist/invalidRequestHandler.js from the image of the IPP version you run, edit it, and mount it back into the container at the same path. A copy from an earlier major version can fail to load.

Customising the response using your Reverse Proxy

You can also choose to customise these responses using your reverse proxy, which might give you more flexibility depending on your use-case.

Here are some examples:

Caddy

https://ipp.example.com {
    reverse_proxy 192.168.1.1:3000 {
        @404 status 404
        handle_response @404 {
            respond "This would be a custom response"
        }
    }
}

Apache

<VirtualHost *:80>
    ProxyErrorOverride On 404
    ErrorDocument 404 /custom_404.html
    Alias /custom_404.html /var/www/html/error-pages/404.html
</VirtualHost>