You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The immich container is placed in a bridged docker network (c.f. compose above), shared with an nginx container. However since this version, since immich only listens on loopback address, the reverse proxy can no longer access immich.
Bug bypass:
Map port 2283 to host (as is done in the compose above - would not be necessary in this setup otherwise), and add host.docker.internal mapping for the reverse proxy container
After docker system prune + server reboot (and reupping everything from scratch) for some reason i'm failing to reproduce any of the above🤔
Immich seems to be working as intended... however the logs are now missleading
With default configuration (so no IMMICH_HOST env var), the log is
immich_server | [Nest] 16 - 12/10/2024, 11:37:50 AM LOG [Api:Bootstrap] Immich Server is listening on http://[::1]:2283 [v1.122.2] [production]
[::1] is technically IPv6 loopback address. The server is however accepting connections from any IP (including v4). Just saying the logs should print [::] instead in this case.
The bug
With
IMMICH_HOST=[::]
, Starting the service generates the following error:When the host is instead set to
IMMICH_HOST=0.0.0.0'
, the setting becomes ignored - the server listens on127.0.0.1
:Similar behaviour for
IMMICH_HOST=::
(note the absence of braces) - the server starts and listens on[::1]
insteadThe OS that Immich Server is running on
Rocky Linux 9 + Docker compose
Version of Immich Server
1.122.2
Version of Immich Mobile App
1.22.2
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Apply
IMMICH_HOST
as per above.Relevant log output
No response
Additional information
The immich container is placed in a bridged docker network (c.f. compose above), shared with an nginx container. However since this version, since immich only listens on loopback address, the reverse proxy can no longer access immich.
Bug bypass:
Map port
2283
to host (as is done in the compose above - would not be necessary in this setup otherwise), and addhost.docker.internal
mapping for the reverse proxy containerAlternatively, hardcode subnet and IP ranges for the network shared with reverse proxy and assign a static IP to immich.
The text was updated successfully, but these errors were encountered: