#SWAG subdomain conf file

1 messages · Page 1 of 1 (latest)

shy dagger
#

hey all,
I got immich working in house, but I want to expose it behind my SWAG instance. This is the immich.subdomain.conf file that I have. When I use this, I get 502 Bad Gateway

https://pastebin.com/1hXpWcSJ

Any thoughts what I am missing? All of my other swag sub domains are working fine
thanks

Pastebin
## Version 2023/05/31# make sure that your container is named - Pa...

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

past fulcrum
#

Take a look at our reverse proxy docs https://immich.app/docs/administration/reverse-proxy

Reverse Proxy | Immich

When deploying Immich it is important to understand that a reverse proxy is required in front of the server and web container. The reverse proxy acts as an intermediary between the user and container, forwarding requests to the correct container based on the URL path.

shy dagger
#

Thank you. I don't know how I missed that. I will look at it when I get home.

shy dagger
#

I just got back around to trying to get immich to work with my current SWAG setup. I am trying to use a combination of the modified _templace.subdomain.conf and the Nginx example config. I am no longer getting the 502 error, but it is just shooting to my homepage, not to immich. I know I am missing something small and stupid, I just can't figure it out. Here is my updated /docker/config/swag/nginx/proxy-confs/immich.subdomain.conf https://pastebin.com/bG1XSq85

Pastebin
## Version 2023/05/31# make sure that your container is named - Pa...

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

serene whale
#

You could not need the second location block, especially if you are still using the immich proxy container

shy dagger
#

if I take out that second location block, I get back to the 502 bad gateway error

shy dagger
#

this link fixed my issue

mossy widget
#

@shy dagger Did this make your /api access for the mobile app work as well? I can still only reach my server when connected to internal LAN

tired agate
#

@shy dagger my config looks pretty much like the first one you posted (I use swag as well), could it be that immich-api was the wrong container name and immich-server was the correct one?