immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 00:30:57 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

[BUG] Can't run immich reverse proxy with IPv6 disabled #683

New Issue
Closed
opened 2026-02-04 21:53:40 +03:00 by OVERLORD · 7 comments
OVERLORD commented 2026-02-04 21:53:40 +03:00
Owner
Copy Link

Originally created by @zackpollard on GitHub (Feb 10, 2023).

Originally assigned to: @zackpollard on GitHub.

The bug

The reverse proxy nginx container will not run if the host has IPv6 disabled. We can solve this by either having an environment variable to disable IPv6 support, or just try to run with IPv6 and if that fails, try IPv4.

The OS that Immich Server is running on

N/A

Version of Immich Server

1.46

Version of Immich Mobile App

N/A

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

N/A

Your .env content

N/A

Reproduction steps

1. Disable IPv6 on host machine
2. Try to run immich 1.46
3. Nginx container will fail

Additional information

No response

Originally created by @zackpollard on GitHub (Feb 10, 2023). Originally assigned to: @zackpollard on GitHub. ### The bug The reverse proxy nginx container will not run if the host has IPv6 disabled. We can solve this by either having an environment variable to disable IPv6 support, or just try to run with IPv6 and if that fails, try IPv4. ### The OS that Immich Server is running on N/A ### Version of Immich Server 1.46 ### Version of Immich Mobile App N/A ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML N/A ``` ### Your .env content ```Shell N/A ``` ### Reproduction steps ```bash 1. Disable IPv6 on host machine 2. Try to run immich 1.46 3. Nginx container will fail ``` ### Additional information _No response_
OVERLORD commented 2026-02-04 21:53:53 +03:00
Author
Owner
Copy Link

@pr0ton11 commented on GitHub (Feb 11, 2023):

This is a regression from #1703

We need a way to configure this without interfering with no IPv6 setups. Also the bug is still present.
I would argue for a way to change the listen parameter to use either 0.0.0.0 (default) or [::] depending on an environment variable.

@pr0ton11 commented on GitHub (Feb 11, 2023): This is a regression from #1703 We need a way to configure this without interfering with no IPv6 setups. Also the bug is still present. I would argue for a way to change the listen parameter to use either 0.0.0.0 (default) or [::] depending on an environment variable.
OVERLORD commented 2026-02-04 21:53:58 +03:00
Author
Owner
Copy Link

@lhhel9l3 commented on GitHub (Feb 12, 2023):

I tried to install immich for the first time using docker-compose, but it's not working, and I think this is the reason. Ipv6 is disabled on my machine

Edit: confirmed. fixed it by downgrading the proxy to 1.45.0. Looked into it and it seems the developers actually KNEW this would break the app in ipv4-only environments, but they pushed the change anyways :-/
https://github.com/immich-app/immich/pull/1577#issuecomment-1422150363

@lhhel9l3 commented on GitHub (Feb 12, 2023): I tried to install immich for the first time using docker-compose, but it's not working, and I think this is the reason. Ipv6 is disabled on my machine Edit: confirmed. fixed it by downgrading the proxy to 1.45.0. Looked into it and it seems the developers actually KNEW this would break the app in ipv4-only environments, but they pushed the change anyways :-/ https://github.com/immich-app/immich/pull/1577#issuecomment-1422150363
OVERLORD commented 2026-02-04 21:54:02 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Feb 12, 2023):

@lhhel9l3 this is part or experimentation and development as we don't have any data of how many people explicit disable IPv6 in their environment. And we want to make IPv6 works for people that need it as well 😀. Now we figure that we have more cases that disable the use of IPv6 so it is time to fix that. I hope it is not too much of a hassle to stay on 1.45 right now

@alextran1502 commented on GitHub (Feb 12, 2023): @lhhel9l3 this is part or experimentation and development as we don't have any data of how many people explicit disable IPv6 in their environment. And we want to make IPv6 works for people that need it as well 😀. Now we figure that we have more cases that disable the use of IPv6 so it is time to fix that. I hope it is not too much of a hassle to stay on 1.45 right now
OVERLORD commented 2026-02-04 21:54:11 +03:00
Author
Owner
Copy Link

@samip5 commented on GitHub (Feb 13, 2023):

@lhhel9l3 You're deploying in a docker-compose setup with the default docker-compose network config, right? If so, yes that has IPv6 disabled as does Docker daemon's default config.

@samip5 commented on GitHub (Feb 13, 2023): @lhhel9l3 You're deploying in a docker-compose setup with the default docker-compose network config, right? If so, yes that has IPv6 disabled as does Docker daemon's default config.
OVERLORD commented 2026-02-04 21:54:35 +03:00
Author
Owner
Copy Link

@lhhel9l3 commented on GitHub (Feb 14, 2023):

Yes, I deploy with the default docker-compose network config, and get ipv6 related errors. I assume this is because ipv6 is disabled via kernel boot options.

When I downgrade the proxy to 1.45.0, the issue is resolved.

@lhhel9l3 commented on GitHub (Feb 14, 2023): Yes, I deploy with the default docker-compose network config, and get ipv6 related errors. I assume this is because ipv6 is disabled via kernel boot options. When I downgrade the proxy to 1.45.0, the issue is resolved.
OVERLORD commented 2026-02-04 21:54:42 +03:00
Author
Owner
Copy Link

@samip5 commented on GitHub (Feb 14, 2023):

I assume this is because ipv6 is disabled via kernel boot options.

Why do people do that?

@samip5 commented on GitHub (Feb 14, 2023): > I assume this is because ipv6 is disabled via kernel boot options. Why do people do that?
OVERLORD commented 2026-02-04 21:54:50 +03:00
Author
Owner
Copy Link

@lhhel9l3 commented on GitHub (Feb 16, 2023):

Fix confirmed, thx

@lhhel9l3 commented on GitHub (Feb 16, 2023): Fix confirmed, thx
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#683
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?