diff --git a/README.md b/README.md index 1ea8347..7143798 100644 --- a/README.md +++ b/README.md @@ -155,6 +155,47 @@ From inside a Docker container, you can't reach another container using `localho [Here's a guide on connecting Docker containers](https://dionarodrigues.dev/blog/docker-networking-how-to-connect-different-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 server IPP is running on, see if you can curl to http://immich_server:2283/api/server/ping and receive a JSON result. +``` + +yet running that same `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). It is a quirk of the musl libc used by the +`node:alpine` base image, not IPP itself. + +Node's `fetch` asks for the IPv4 (A) and IPv6 (AAAA) records at once. If your resolver answers the AAAA query +with `NXDOMAIN` instead of the correct empty `NOERROR`, musl fails the whole lookup - even though the IPv4 +address is valid - and IPP reports the connection as failed. `curl` and glibc (the non-alpine `node` image) +tolerate this, which is why curl works and this only shows up here. The underlying error, hidden behind the log +message above, is `getaddrinfo ENOTFOUND`. + +The reliable fix is to disable IPv6 for the container so only the IPv4 lookup happens. Add this to your service +in `docker-compose.yml`: + +```yaml +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. + +See issues [#203](https://github.com/alangrainger/immich-public-proxy/issues/203) and +[#263](https://github.com/alangrainger/immich-public-proxy/issues/263) for the full investigation. + ## Feature requests You can [add feature requests here](https://github.com/alangrainger/immich-public-proxy/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop),