#troubles moving server
1 messages · Page 1 of 1 (latest)
:wave: Hey @meager furnace,
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
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker ps -adocs - 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...
- :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: read applicable release notes.
- :ballot_box_with_check: reviewed the FAQs for known issues.
- :ballot_box_with_check: reviewed Github for known issues.
- :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
- :ballot_box_with_check: uploaded the relevant information (see below).
- :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 -landdf -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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:
also i'm a bit confused why there's 2 library checks, one passes and one doesn't but that seems to be the same on the screenshots provided in the guide..
The first check is just whether it has write access, the second is to see if all the files are there
Have you got any custom volume mounts going on or such? Are you sure you've moved all files, including hidden ones?
yes i used cp -r to move the whole DB also i don't have custom volumes set up
this is on my old server i'm migrating from:
bl4ze@homeserver2:/mnt/media/Immich/Photos/library$ ls -a
. .. .immich
and this on the new one i'm migrating to:
bl4zee@servarr:~/storage/Immich/Photos/library$ ls -a
. .. .immich
i'm assuming this is the folder getting checked?
what even is supposed to be in there? when i cat that file it's just a string
it is only relevant to anyone using storage template
that's why it's only a warning
maybe the message there could be a bit more verbose
yeah ik, it seems fine to ignore here, but I don't think it should be triggering anyways right?
so i can just press next?
if you're not using storage template, which i don't believe you are, you should be good to go
hm
to be fair we could hide that warning if the upload folder succeeds
and vice-versa