Backup frozen, no sign of anything.
Nothing is getting backed up. I checked the server on my windows 11 machine and I see no running jobs.
I reinstalled the appa few times from GitHub. I installed v1.133.1 of the "app-arm64-v8a-release.apk" for my android phone, since my local server is running this version.


45 Replies
:wave: Hey @dr.fish.,
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.im not sure how to troubleshoot, but ive uninstalled and reinstalled many times, i made sure the server and app are of the same version. ive logged in with my local ip and also used my domain, however, i got the same issue.




We don't really support old versions at the moment. I encourage you to update to the latest version, switch to the beta timeline and use it
the logs are moving too fast for me to see anything. so idk whats going on.
ah, ok, ill try work on that...
i stopped cause there was a breaking change i wasnt sure how to implement.
v1.136.0
Do you have a specific question?

what is this "IMMICH_MEDIA_LOCATION"
You literally left the important part out lol
ik i dont have it and its prob not important since ive lived without it, but like how does it help having it?
It doesn't "help"
Some installs just happen to have it set, so in that case it'd be breaking
i should have asked "in which way does it help having IMMICH_MEDIA_LOCATION"
It doesn't
In any way
ahh i see
We just introduced it at some point for reasons and for instance the all in one image started setting to change the paths in their custom-built containers
There's no benefit to it whatsoever
ahh gottchu
i guess its one of thoes super rare small what if moments? or? xD
Yeah pretty much
It'd also be relevant for bare metal installs
Stuff like the (unofficial) nixpkg
its nice knowing u implement small things that seem irrellivant but MAY help someone out there
Note: if you DO NOT have IMMICH_MEDIA_LOCATION in your .env file, or if it is set to a path that starts with a / (absolute path), THIS BREAKING CHANGE DOES NOT APPLY TO YOU.This should be a fairly easy decision tree though You don't have it? - Cool, don't bother
yup, i guess it was me questioning if i should implement it or not xD
We probably wouldn't these days :KEKW:
but i got the answer.
:PepeHands:
thats cool too, yall are buzzy bees
Gotta balance complexity with how many users would benefit from it :)
yup. and balance is the key word here

can i ask
stupid question, but like, is the upload folder a temp folder where pics and videos stay ready to be uploaded and backed up or smth?
Can you be specific about "upload folder"? As you can see in your screenshot it was very ambiguous with the old paths 😅
ahh, sorry, this is v1.137.0

im not sure, cause in my compose file, its "app/upload", not "upload/upload"
so idk if i done smth wrong TT
Read your screenshot again :D
ik it says not to change this area.
I mean this screenshot
hmm, it says "It will now be located at /data/upload"
ur talking about this, right?
No, it says
The default compose file now usesYou currently have/data
instead of/usr/src/app/upload
/usr/src/app/upload
So why this confusion?ok so like, i need to manually change it from /app to /data
i didnt see that part xD
But more impoortantly
This is a completely optional and NOT a breaking change
yeah
Read the whole thing
im really slow, ig ill just leave it, idk...
Where are you stuck at currently?
This should give you all the information you need
Really you only care about the first paragraph