#nginx

1 messages · Page 1 of 1 (latest)

novel steppe
#

thank

harsh crestBOT
#

:wave: Hey @novel steppe,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

novel steppe
#

Hello

#

I have problem with exposing immich through npm proxy manager

#

504 error

thin leaf
#

first question. is npm and immich on the same docker network

late skiff
novel steppe
thin leaf
#

first you need to list off your docker networks thats docker network ls

#

but please fill in the rest of the details that were asked by Daneil and the other staff

novel steppe
#

1468052112af immich_default bridge local
3d9d66dddc15 matrix_net bridge local
bb1838a4a22f nginx-pm_default bridge local

#

looks same

thin leaf
#

so no they are likely not on the same docker network

novel steppe
#

different network id

thin leaf
#

you can do a docker network inspect immich_default this will tell us whats on that network and then docker network inspect nginx-pm_default and then docker network inspect matrix_net

late skiff
#

If only there was a way to just see the compose file :)))

thin leaf
#

and what daniel said

#

your compose file would be very valuable here

novel steppe
thin leaf
#

and your compose file?

novel steppe
#

my com pose yml:

late skiff
#

Oh let me guess. Did you enter 192.168.x.x in NPM for the ip address?

novel steppe
#

yes

thin leaf
#

what OS are you running all this in?

late skiff
novel steppe
#

ubuntu 22 lts

late skiff
#

Docker containers cannot access the host's network interface

thin leaf
novel steppe
#

some of my proxies works like that, i dont know why

late skiff
#

What you want is add immich_server to the proxy network and then use http://immich_server:2283 in NPM

late skiff
thin leaf
#

docker networking is a bit weird if you have little to no experience with virtualization

novel steppe
#

like that?

thin leaf
#

and even if you did have that experience its not all useful when comparing it to docker

thin leaf
novel steppe
#

still not working

late skiff
#

I think learning the docker basics is doable though

novel steppe
#

EVEN WORSE NOW

late skiff
#

You have a DNS issue

#

That's not related to anything we've just done lol

novel steppe
#

how to fix that?

late skiff
#

How do I fix my car?

thin leaf
#

go watch those vidoes I just shared with you

#

you gotta understand what you are working with before you go off deploying stuff let alone trying to fix it

novel steppe
#

ok, thx

#

502 Bad Gateway now

thin leaf
#

to give you a bit of a leg up. I append this at the end of all my docker containers networks: default: name: <your docker network name goes here> external: true

novel steppe
#

should I have mutual network to all stuff I want to expose?

thin leaf
#

yes and no

#

just depends on the use case. but generally if you want the containers to be able to talk to one another they have to be on the same network

novel steppe
#

ok

thin leaf
#

you can create one manually if you would like. this way you know what to put into your compose file

#

docker network create <name of network>

novel steppe
#

thx

#

I will watch first that vids

thin leaf
#

then append at the end of each of your docker compose files networks: default: name: <that network name you just created> external: true

#

good. networkchuck explains what the difference is between the default docker network and one that you create.

#

hes also very energizing lol

novel steppe
#

I learned, that I can run npm with host network to simplify things

#

But I cant fin docker-compose of my npm

#

jc21/nginx-proxy-manager latest 9c3f57826a5d 16 months ago 843MB

novel steppe
#

I ran docker up proxy manager and it looks like clean setup

#

I dont know where last configs are stored

thin leaf
#

wouldnt suggest doing host

novel steppe
#

I know, i dont even know how to do that

#

I mean i compsed it with host network name, but i do not know how to check it

#

I think I need more basic knwledge about how docker works

#

these videos are to fast for me to understand this

#

Do you guys have good docker networks explainer with images and graphs?

thin leaf
#

I've given you the inspect commands above. that will let you see what docker containers you have on which network

#

docker network create will create a docker network with what ever name you give it

#

And I've given you the network bit you would need to add to your compose files so you can attach your container to whatever docker network you create

#

You could also use the docker network connect command to manually connect a container to a specified network