Immich integration not working

[lcosmin]

Bug Description

Integration with Immich 3.1.0 doesn't seem to work with AL (0.13.0). It succeeds when adding it, but I'm unable to see any photos.

Steps to Reproduce

1. Create a new Location
2. Try to use Immich to add image (by any means: date, album, search)

Expected Behavior

I expected to see images, but I only see empty thumbnails. Fetching the albums list seems to work, but no photos are actually displayed.

Screenshots / Logs

Logs don't show much:

...
adventurelog-backend   | 2026-08-26 13:09:11,380 INFO supervisord started with pid 1
adventurelog-backend   | 2026-08-26 13:09:12,382 INFO spawned: 'cron' with pid 46
adventurelog-backend   | 2026-08-26 13:09:12,384 INFO spawned: 'gunicorn' with pid 47
adventurelog-backend   | 2026-08-26 13:09:12,386 INFO spawned: 'memcached' with pid 48
adventurelog-backend   | 2026-08-26 13:09:12,387 INFO spawned: 'nginx' with pid 49
adventurelog-backend   | [2026-08-26 13:09:12 +0000] [47] [INFO] Starting gunicorn 23.0.0
adventurelog-backend   | [2026-08-26 13:09:12 +0000] [47] [INFO] Listening at: http://[::]:8000 (47)
adventurelog-backend   | [2026-08-26 13:09:12 +0000] [47] [INFO] Using worker: sync
adventurelog-backend   | [2026-08-26 13:09:12 +0000] [60] [INFO] Booting worker with pid: 60
adventurelog-backend   | [2026-08-26 13:09:12 +0000] [61] [INFO] Booting worker with pid: 61
adventurelog-backend   | 2026-08-26 13:09:13,908 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
adventurelog-backend   | 2026-08-26 13:09:13,908 INFO success: gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
adventurelog-backend   | 2026-08-26 13:09:13,908 INFO success: memcached entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
adventurelog-backend   | 2026-08-26 13:09:13,908 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
adventurelog-backend   | [Location Geocode Thread] Starting geocode for location 46c397a0-6a7e-4a7e-8d02-4bcd50291a2a
adventurelog-backend   | Not Found: /api/integrations/immich/search/
adventurelog-backend   | Forbidden: /api/integrations/strava/activities/
adventurelog-backend   | Not Found: /api/integrations/immich/search/

Platform

Docker

Install Method

Docker Compose

AdventureLog Version

v0.13.0

Reverse Proxy

Caddy

Docker Compose / Relevant Variables (Optional)

SITE_URL=https://xxx.xxxxxx.com

Additional Context

Used the advanced setup because I wanted to use an external postgres database.

Confirmation

• I searched existing issues and confirmed this is not a duplicate.

[seanmorley15]

Hello @lcosmin, are you able to double check the URL you put in for the Immich server? Since the AdventureLog container needs to reach the Immich container make sure that address is accessible to AdventureLog where it's hosted. Let me know if you have any questions about this

[lcosmin]

I connected to the docker frontend container and ran this:

/app $ node -e "fetch('https://immich.mysite/api').then(async r => console.log([...r.headers.entries()], '\n' + a
wait r.text()))"
[
  [ 'alt-svc', 'h3=":443"; ma=2592000' ],
  [ 'content-length', '29' ],
  [ 'content-type', 'application/json; charset=utf-8' ],
  [ 'date', 'Thu, 10 Sep 2026 12:43:02 GMT' ],
  [ 'etag', '"1d-8ETZZANMbjAMETpmcA1y4dIfCN0"' ],
  [ 'vary', 'Accept-Encoding' ],
  [ 'via', '1.1 Caddy' ],
  [ 'x-correlation-id', 'lam99cox' ],
  [ 'x-powered-by', 'Express' ]
]
{"message":"Cannot GET /api"}
/app $ node -e "fetch('https://immich.mysite/api/albums').then(async r => console.log([...r.headers.entries()], '\n' + await r.text()))"
[
  [ 'alt-svc', 'h3=":443"; ma=2592000' ],
  [ 'content-length', '37' ],
  [ 'content-type', 'application/json; charset=utf-8' ],
  [ 'date', 'Thu, 10 Sep 2026 12:46:09 GMT' ],
  [ 'etag', '"25-SetIB6wLsPt3Ogr5oCd0XHpTaMw"' ],
  [ 'vary', 'Accept-Encoding' ],
  [ 'via', '1.1 Caddy' ],
  [ 'x-correlation-id', 'b88zuuy6' ],
  [ 'x-powered-by', 'Express' ]
]
{"message":"Authentication required"}

So, my immich instance is reachable. In adventurelog, I configured the url as https://immich.mysite/api, as documented here.

Tested a few endpoints and they are available under https://immich.mysite/api/{endpoint} (meaning the Immich API seems to be accesible)