#Trying to update immich

1 messages · Page 1 of 1 (latest)

crisp quail
#

So put in the latest docker-compose.yml file and run the two commands docker compose pull and docker compose up -d, though now when going to my server it asks to setup a new admin account because its my "first time"
im gonna guess i really messed something up?

north aspenBOT
#

:wave: Hey @crisp quail,

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 immich.

References

Checklist

  1. :blue_square: I have verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: I have read applicable release notes.
  3. :blue_square: I have reviewed the FAQs for known issues.
  4. :blue_square: I have reviewed Github for known issues.
  5. :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the /upload command.
  7. :blue_square: I have 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)

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

thick plinth
#

Did you change anything in your yml or env files?

spring lark
#

Did you read the release notes?

crisp quail
spring lark
#

You should read the notes for every version you're skipping, not just the very latest ;)

thick plinth
#

I think you can restore your database
Just put the values back to what they were.
Your database is probably still inside the container

crisp quail
crisp quail
#

is there any special thing i should do or just put back the old compose file and repeat the same steps as if i was "updating"

thick plinth
#

Nothing special is needed for this update.

just put back the old compose file and repeat the same steps as if i was "updating"

crisp quail
#

yaml: line 34: found character that cannot start any token

#

this is the error im getting when running docker compose pull with my original docker-compose file back in

north aspenBOT
thick plinth
north aspenBOT
thick plinth
#

Pay attention to the indentation (original file on the right, your file on the left)

crisp quail
thick plinth
crisp quail
#

gotcha xD sorry i think ill fix it now and figure it out thanks sorry for the dumbass mistake

thick plinth
#

In any situation I always use VScode

crisp quail
#

ya i had it idk why i delete it, i just dont do coding much at all, i will look into that and fix it thanks for the help!