#immich v1.125.7 all docker container stay in heslthy state instread of running

1 messages · Page 1 of 1 (latest)

shut sail
#

Hi, after an update I have all container blocked in healthy state instread of running but I can't see any kind of error in the container logs.

Thanks

wise kestrelBOT
#

:wave: Hey @shut sail,

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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :ballot_box_with_check: 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.

untold pagoda
#

Healthy is a “higher” run state than running. What’s the actual issue?

shut sail
#

I can't reach the server on port 2283 (even if I didn't chenge the configuration and the proxy works well - even the local ip is correct) so I thouth that the problem was the "healthy" state because other services ( not immich) work correctly and are in running state.

So thank a lot and sorry for the question ( and my poor english), I'll check better the infrastructure

fast lotus
#

How old was your previous version? Did you see the port change for 3003 to 2283 in the compose file?

shut sail
#

my last version was 1.122.0 and the port binding is 2283:3001 and if a go to IP_machine:2283 I can't reach it. That's strange because I used portainer stack and just uploaded the stack, I didn't touch anything in the network config

fast lotus
#

Should be 2283:2283 @shut sail

#

It changed in version 118 so I am confused 122 would have worked at all

shut sail
#

sry maybe my mistake and i was on 118