5.9 KiB
Troubleshooting
Video playback
If you're using Cloudflare and videos do not play well, set your /share/video/* paths to bypass cache. See
this Cloudflare community thread
for the background.
"Download all" fails partway through
If you use Cloudflare with a "cache everything" rule and large zip downloads stop with a browser error after a few
seconds, add a cache rule that bypasses cache for /share/*/download and /s/*/download, the same as for
/share/video/* above. The zip is streamed as it is fetched from Immich, and Cloudflare's cache cuts those downloads
short.
IPP sends the zip with Cache-Control: no-store, which is enough on its own if your cache rule's Edge TTL is set to
respect the origin. If the rule overrides the Edge TTL, Cloudflare ignores that header and you need the bypass rule.
Uploads fail with "Too large for this server"
Something in front of the upload service refused the file before it arrived. The upload service's own limit gives a different message that names the size.
- Cloudflare refuses requests over 100 MB on the Free and Pro plans, Cloudflare Tunnel included. Set
upload.maxFileSizeto100so the upload page turns away larger files before sending them, with a message that says the limit. - nginx allows 1 MB by default. Set
client_max_body_sizeto at leastupload.maxFileSize.
See Request size limits.
Link previews show http:// or a private IP
The gallery itself uses relative URLs, so it works behind any reverse proxy. The one place IPP needs a fully qualified
URL is the og:image tag that messaging apps use for link previews. Without PUBLIC_BASE_URL, IPP builds it from the
incoming request, and behind a TLS-terminating reverse proxy that request arrives as plain http:// on whatever
hostname or IP the proxy used.
Set PUBLIC_BASE_URL in your docker-compose.yml to the public address of IPP, without a trailing slash:
environment:
PUBLIC_BASE_URL: https://your-proxy-url.com
If you serve IPP from several domains, leave it unset and make sure your reverse proxy forwards the original Host
header. See Running on a single domain.
Container won't start after mounting config.json
Docker refuses to start the container, with an error that ends:
Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
The file on the left of the volume line doesn't exist. When the source of a bind mount is missing, Docker creates an
empty directory in its place, and a directory can't be mounted over the config.json file inside the image.
Check that your config.json is at that path. A relative path such as ./config.json resolves from the folder that
holds docker-compose.yml. A Portainer stack resolves it inside Portainer's own data folder instead, so use an
absolute path there:
volumes:
- /opt/immich-public-proxy/config.json:/app/config.json:ro
Delete the empty directory Docker created, then recreate the container. See #83.
Can't reach Immich using localhost:2283
This is a normal Docker thing, nothing to do with IPP.
From inside a Docker container, you can't reach another container using localhost. You need to use a Docker network
IP or your server's IP address.
Here's a guide on connecting Docker containers.
IPP logs "Unable to reach Immich", but curl inside the container works
If IPP can't connect to Immich even though the container clearly can, you'll see this in the logs:
Unable to reach Immich on http://immich_server:2283
From the container IPP is running in, run this and check you receive a JSON result: node -e "fetch('http://immich_server:2283/api/server/ping').then(r => r.text()).then(console.log).catch(console.error)"
Avoid testing with curl - curl uses its own DNS resolver and can succeed even when the resolver Node/IPP uses (musl getaddrinfo) fails.
yet curl from a shell inside the container succeeds:
/app $ curl http://immich_server:2283/api/server/ping
{"res":"pong"}
This happens with both Docker Compose service names (like immich_server) and hostnames from a local DNS resolver
(for example an AdGuard Home or dnsmasq CNAME rewrite). The cause is the DNS lookup, not IPP: Node asks for the IPv4
and IPv6 addresses at once, and if your resolver answers the IPv6 query with NXDOMAIN instead of an empty NOERROR,
the Alpine base image fails the whole lookup even though the IPv4 address is fine. curl tolerates this, which is why
it works from a shell and why the log suggests the node -e command instead: it uses the same resolver as IPP, so it
fails the same way. The underlying error is getaddrinfo ENOTFOUND.
The reliable fix is to disable IPv6 for the container, so only the IPv4 lookup happens. Add the sysctls block to
your service in docker-compose.yml:
services:
immich-public-proxy:
image: alangrainger/immich-public-proxy:latest
# ...your existing config...
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
- net.ipv6.conf.default.disable_ipv6=1
Alternatively, point IMMICH_URL at Immich's IP address (a numeric address skips DNS resolution entirely), or fix
your resolver to return an empty NOERROR (NODATA) rather than NXDOMAIN for the missing AAAA record.
