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
I have been using Docker containers together with Nginx Proxy Manager for a long time so that I don’t always have to use the full IP with port locally, but can simply use a domain, e.g., immich.local. This worked well until a few days ago, but I had to perform a hard restart because the server had completely frozen. After the restart, everything seemed to work fine, but I noticed that I could only reach some containers by IP, and when accessing via domain, I got a 502 - Bad Gateway error (containers on the bridge network did not work, while containers on br0, such as Nginx, continued to function). Nothing was changed in the settings, and after some research, I discovered that sometimes the setting “Host access to custom networks” might need to be reset. Unfortunately, that was not the solution.
What I Have Done So Far
Turned Host access to custom networks off and on again.
Placed all containers into their own network for better clarity.
Nginx continues to run on br0 with its own IP but received the post-argument && docker network connect atlasnet Nginx-Proxy-Manager-Official so that it can access the other network.
Completely deleted the old Nginx container along with the data under Appdata (perhaps something got corrupted during the hard restart).
In Adguard, I created a DNS rewrite for the domain immich.local, which is then forwarded to 192.168.178.13.
In Nginx, I set up a proxy host with the domain immich.local that points to the address http://192.168.178.132:8085.
If I have forgotten any information or you need to know anything else, please let me know. I don't know what else I can do. Does anyone have any ideas?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey guys,
I have been using Docker containers together with
Nginx Proxy Manager
for a long time so that I don’t always have to use the full IP with port locally, but can simply use a domain, e.g.,immich.local
. This worked well until a few days ago, but I had to perform a hard restart because the server had completely frozen. After the restart, everything seemed to work fine, but I noticed that I could only reach some containers by IP, and when accessing via domain, I got a 502 - Bad Gateway error (containers on thebridge
network did not work, while containers onbr0
, such asNginx
, continued to function). Nothing was changed in the settings, and after some research, I discovered that sometimes the setting “Host access to custom networks” might need to be reset. Unfortunately, that was not the solution.What I Have Done So Far
Nginx
continues to run onbr0
with its own IP but received the post-argument&& docker network connect atlasnet Nginx-Proxy-Manager-Official
so that it can access the other network.Nginx
container along with the data underAppdata
(perhaps something got corrupted during the hard restart).How Domain-Based Access Works
Immich
runs on IP192.168.178.132:8085
(the Unraid address),Nginx
on192.168.178.13
, andAdguard Home
on192.168.178.42
.Adguard
, I created a DNS rewrite for the domainimmich.local
, which is then forwarded to192.168.178.13
.Nginx
, I set up a proxy host with the domainimmich.local
that points to the addresshttp://192.168.178.132:8085
.If I have forgotten any information or you need to know anything else, please let me know. I don't know what else I can do. Does anyone have any ideas?
Beta Was this translation helpful? Give feedback.
All reactions