Update docs

This commit is contained in:
Alan Grainger
2026-10-07 16:51:46 +13:00
parent ba893dc42f
commit 7a9ff2e6ee
12 changed files with 53 additions and 66 deletions
+14 -23
View File
@@ -2,22 +2,21 @@
## Video playback
If you're using Cloudflare and having issues with videos not playing well, make sure your `/share/video/` paths are
set to bypass cache. I ran into this issue myself, and found
[some helpful advice here](https://community.cloudflare.com/t/mp4-wont-load-in-safari-using-cloudflare/10587/48).
If you're using Cloudflare and videos do not play well, set your `/share/video/*` paths to bypass cache. See
[this Cloudflare community thread](https://community.cloudflare.com/t/mp4-wont-load-in-safari-using-cloudflare/10587/48)
for the background.
<a href="/cloudflare-video-cache.webp"><img src="/cloudflare-video-cache.webp" style="width:70%" alt="Cloudflare cache bypass rule for video paths"></a>
## "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 slug-link form), the
same as for `/share/video/*` above. From v3.3.0 the zip is streamed as it is fetched from Immich, and Cloudflare's
cache cuts those downloads short.
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.
Versions after v3.3.0 send 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.
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.
## Link previews show `http://` or a private IP
@@ -85,17 +84,13 @@ yet running that same `curl` from a shell inside the container succeeds:
```
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.
(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. The underlying error is `getaddrinfo ENOTFOUND`.
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 the `sysctls` block to your
service in `docker-compose.yml`:
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`:
```yaml
services:
@@ -112,7 +107,3 @@ your resolver to return an empty `NOERROR` (NODATA) rather than `NXDOMAIN` for t
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.
---
I use Linux/Android, so this project is tested with BrowserStack for Apple/Windows devices.