Cannot Start Immich Server (Error 1) TypeORM, Won't Boot At All
Hello, hoping somebody can help as I am running into signifigant issues with running immich. It cannot seem to access the database. I see a link in the error to the documentation where it says this is a known issue and that the database file needs to be run at least once on a lower version before updating https://immich.app/errors/#typeorm-upgrade
It before was "image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}"
I have tried changing it to "image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:- 1.132.0}" as well as "image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:- 1.136.0}" but it just seems to start as 1.138.1 no matter when I run "docker compose up"
When I go into my docker-compose.yml file and set the version to these lower versions (as it needs to be run at least once between versions 1.132.0 and 1.136.0) it still does not work. Am I setting the specific version right in my docker-compose.yml file? Am I missing somethiing on downgrading?
I am trying to do the downgrade trick because I am getting the "breaking" TypeORM error but am very confused. No matter how I seem to format the version on the docker-compose.yml file it is still giving me the same error and saying in the log (shared in the attachment) that it is "immich_server Initializing Immich v1.138.1" and cant seem to downgrade? Is there additional steps to downgrading I am missing? Is there more to it than stopping all running instances with "docker compose down" and then trying to run it again with the edited docker-compose.yml file or am I not specifying the version number properly? Like why is it still trying to run 1.138.1 after I changed this info in the compose file? I just need to run the lower version once to fix the database so I can upgrade to the latest version again and get past this database issue.
I am so stuck, I have tried following the documentation best I can, any input would be greatly appreciated, thanks! Attached log is from after changing version.
19 Replies
:wave: Hey @Sumo,
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
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
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.immich versions start with v
So if you want to try and pull
v1.132.0 it needs to be in this format
try pulling v1.136.0 for starters 🙂Also, you're only replacing the default. So if
IMMICH_VERSION is set it'll never use thoseCan you elaborate on this? I don't understand
This is what I currently have my docker compose file set to after adding the v
"services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:- v1.132.0}"
And I am still getting the same error it is still booting as "Initializing Immich v1.138.1"
I just don't understand the formatting i'm supposed to be using here I couldn't find it in the docs
${IMMICH_VERSION:~v1.132.0} means "use the env variable IMMICH_VERSION, and if that does not exist fall back to v1.132.0"Do I have to do anything past changing docker compose file and then "docker compose down", "docker compose up" after changing the version?
Hold on let me see if I understand what you are saying? I'm still a little confused sorry I do really appreciate the help
You are saying to format like this?
"services:
immich-server:
container_name: immich_server
image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:~v1.132.0}"
I am getting new errors this way with
"invalid interpolation format for services.immich-server.image.
You may need to escape any $ with another $.
ghcr.io/immich-app/immich-server:${IMMICH_VERSION:~v1.132.0}" so i'm going to guess I still don't have the formatting right for the version
What? I'm not saying the formatting is wrong
I'm saying that it'll use the version in your
.env file
Not the version you're changing thereohhhh
Go read about environment variables and variable interpolation in docker compose
These are fundamental basics
I am brand new to this I am really doing my best to wrap my head around things here
This is my first docker compose program
FWIW Immich is not a good fit for people new to self hosting. You're dealing with very important data here that you absolutely do not want to lose
I have all of my pictures on a regular scheduled backup with ffs for reasons like this
I haven't had a lot of other troubles thus far
I do run jellyfin and that as well but never had a single problem there. Docker is usually quite simple it can just get a little complicated when things fall apart sometimes
:monkaW: where did you get FreeFileSync from? 1990 has called and wants its tools back lol
Hey i'm a first year linux user here lol if you have any better foss alternatives i'm all ears.
Just trying to get out of this shitshow system that we have all been forced into and keeps getting stronger and stronger every year with their tracking. I also made the stupid mistake of starting with manjaro on an unencrypted drive instead of hopping right to arch but sometimes we gotta learn our lessons the hard way. I have put a shit ton of work getting this far just out of being a spyware windows user all my life
restic and borg are popular recommendations :PThank you!
ugh okay so I thought we were doing good after modifying the .env but apparently not
That is progress though. A recent DB migration has surfaced a bunch of issues with people's databases. This is one case of that
@Sergey Katsubo do you have the script at hand to clean those up?
This should do the job:
1. Connect to the database
2. Then run these SQL commands: