#Just Upgraded with Issues in Yacht but after full update no access!
1 messages · Page 1 of 1 (latest)
:wave: Hey @lucid nymph,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Typesense: You can't fix this. Just wait until we get rid of it. Sorry.
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :ballot_box_with_check: I have reviewed the FAQs for known issues.
- :ballot_box_with_check: I have reviewed Github for known issues.
- :ballot_box_with_check: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :ballot_box_with_check: I have tried an incognito window, 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)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
No access via local ip or web domain address
did you update your docker compose file?
yeah you need to change your docker compose yml
https://github.com/immich-app/immich/releases/tag/v1.91.0
go in the folder where your docker files are and do docker compose logs -f
If you're gonna say in the checklist that you read the release notes then you should actually do that as well ;)
we already know the issue though no need just do whats said in the release 1.19.0
for the future: before updating check what changes
i cannot copy the log it has over 3000 lines
dont bother with the logs, adjust your docker-compose.yml
ok
if it still doesnt work after changing the docker-compose.yml you can send the logs though
looks good I think
whats to command to restart and update all containers via terminal i forget i use yacht portainer most of the time 🙂
docker compose down
docker compose pull
docker compose up -d
ah
remove line 17 on your docker compose
- typesense
and it should work without sudo if you setup docker correctly if not sudo should make it work
try docker compose down --remove-orphans
looking better but 1 errror re db https://xbackbone.osopolar.cloud/VIDE3/gEbiloNU18.
can you go on the web interface?
yes
when booting it might give some db errors cause the db didnt start yet so thats normal