[HOW-TO] Immich: How to Change Your Immich Upload Directory and Other Useful Tips

[vhsdream]

Immich in an LXC

Love Immich? Hate Docker? Me too! That's why I wanted a Proxmox Helper Script for the best open-source, self-hosted photo management software to ever exist.

So the script is here, and it seems to work, and it's huge and kind of complex. Let's go over what the script CAN do and what it CANNOT do.

✅ Can do

• Install Immich, as an unprivileged (default) or privileged LXC.
• Setup hardware-accelerated transcoding (QuickSync/VAAPI) if you have a modern Intel CPU/iGPU AND if you have made the proper modifications to your Proxmox host (not covered in this guide). All you need to do is turn this on in the Immich Settings panel.
  • (It might also be able to do transcoding (VAAPI) with an AMD CPU/iGPU?).
• Setup hardware-accelerated machine-learning (Smart Search, Facial Recognition) with OpenVINO, if you have a compatible Intel CPU/iGPU.

🚫 Cannot Do

• Setup hardware-accelerated transcoding or machine-learning with NVIDIA/AMD/Rockchip GPU/APUs. Perhaps subject to change.
• Setup a custom Immich media upload folder that differs from /opt/immich/upload.
• Your laundry or your taxes.

Since so far we've been receiving feedback that the major problem people are having is related to using a different upload folder (with good reason!), this guide is mainly geared towards attempting to demystify that part.

📁 The upload Folder

It's located by default in /opt/immich/upload, on the same disk as the LXC itself. Definitely not ideal, since you're gonna have to continuously increase the size of the disk as you add more media. I'd wager that pretty much all of us use some kind of NAS, which is likely on completely different disks, and that's where we want to store our Immich uploads.

It defaults to where it does because there are many different ways to configure storage on Proxmox, and the script is unable accommodate them as well as properly setup permissions in each use case. So this is left up to you to figure out. That being said, this guide is not going to cover how to properly mount a network share in your LXC, aside from the fact of whether you should choose to create an unprivileged LXC or a privileged LXC.

❓ Choose Privileged if...

• You understand and accept the security risks of doing so. Not going into that here.
• You already have privileged LXCs with mounted external shares and you know how they work.
• You want more of an "Easy Mode" for ensuring the immich user can write to the share.

❔ Choose Unprivileged (default and recommended) if...

• You know how to edit the LXC configuration file for Immich with UID and GID mapping configs.
• You know how to add bind mounts to the LXC configuration file.
• You are comfortable with modifying /etc/subuid and /etc/subgid entries on your Proxmox host.

Needless to say, regardless of the path you choose, you should have this figured out before proceeding. But to be a good sport and to get you started, I'll say you need to learn about how unprivileged LXCs operate in relation to the host, and how to leverage that to be able to mount a writable share in your Immich LXC. Try this writeup for a good starting point. And now, the GUIDE.

⚙ Changing the Immich upload directory in your Immich LXC

1. Stop Immich services
   systemctl stop immich-web immich-ml
2. Edit your Immich .env file (/opt/immich/.env) to reflect your chosen mount point
   nano/vi /opt/immich/.env
   Look for IMMICH_MEDIA_LOCATION and change it to the path of your bind mount.
   For example, say your bind mount is at /mnt/immich. Do this:

IMMICH_MEDIA_LOCATION=/mnt/immich

Save and close the file.

3. Copy all folders from the old upload directory to the new one, especially if you already have uploaded data. This is the easiest method, and it also proves that at least the root user can write to the folder. Even if you haven't uploaded data, there are files in each of those folders that must also be present for this to work.
   cp -a /opt/immich/upload/* /mnt/immich (or whatever your location is)
   You want the folder structure to look like this:

root@immich-dev:~# tree -a -L 1 /mnt/immich/
/mnt/immich/
├── backups
├── encoded-video
├── library
├── profile
├── thumbs
└── upload

And within each of those dirs there should be an .immich file, and potentially a folder with a long alphanumeric name which is your user ID, if you have existing uploaded content.

4. Recreate some symlinks. This is the step I was missing for those who were having issues. I didn't think of it because I have a slightly different setup (which I'll explain below).

Delete these symlinks:

rm /opt/immich/app/upload
rm /opt/immich/app/machine-learning/upload

Recreate them so they point to your new location:

ln -sf </mnt/immich> (or whatever your location is) /opt/immich/app/upload
ln -sf </mnt/immich> (or whatever your location is) /opt/immich/app/machine-learning/upload

So the folders should look like the below:

root@immich-dev:/opt/immich# tree -a -L 1 app/ app/machine-learning/
app/
├── bin
├── dist
├── geodata -> /opt/immich/geodata
├── LICENSE
├── machine-learning
├── node_modules
├── package.json
├── package-lock.json
├── resources
├── start.sh
├── upload -> /mnt/immich
└── www
app/machine-learning/
├── ann
├── immich_ml
├── ml_start.sh
├── ml-venv
└── upload -> /mnt/immich

5. Confirm ownership of the Immich folder in case it's changed.
   chown -R immich:immich /opt/immich

6. NEW STEP as of v1.136.0/July 31 2025. Apparently changing your IMMICH_MEDIA_LOCATION can wreak some havok on how immich now handles path management. In their efforts to get to stable and to have a more sane handling of paths, with v1.136.0+ (actually I noticed something funny with some paths a couple versions earlier) you may need to run the following in order to have all your images/videos/thumbnails appear.

cd /opt/immich/app/bin
./immich-admin change-media-location

This will start an interactive script that allows you to update the path of assets in the DB from relative to absolute. Right now I can't tell if running this is absolutely necessary, but one tip off that you might need to is if you see lots of blurry thumbnails, or if you go to zoom into an image on the web and it suddenly disappears.

I should also note that it's OK to run this later on, well after you've changed the location; just make sure that Immich services are stopped before you do it.

ANOTHER UPDATE - literally as I posted the above, a new version dropped which apparently will detect a change to IMMICH_MEDIA_LOCATION and will do the above for you automatically.

7. Restart Immich services and tail the web log, then go check out your Immich feed and open an image.

systemctl start immich-ml immich-web
tail -f /var/log/immich/web.log

You need to check Immich because if you messed up or skipped the symlink thing, if you only check the log things will seem fine. As soon as you try to look at your timeline (all thumbnails blurred) or open a photo (it won't load), then you'll see the problem.

8. Once you are convinced it's all working (maybe upload a new photo), then you can delete the previous upload folder.
   rm -rf /opt/immich/upload

That should be it.

📝 A Note About Updating

During the update process, the script deletes everything in the /opt/immich/app/ directory, including those symlinks. But they get recreated, using the information from your .env, where IMMICH_MEDIA_LOCATION will point to your current upload directory! So you do not need to recreate anything yourself.

🚀 Advanced Settings

I mentioned earlier that my setup is a bit different, which caused me to overlook the symlink step. I actually have not changed IMMICH_MEDIA_LOCATION in my .env file. Instead I made an additional symlink from /opt/immich/upload/upload to my bind mount. I did this because I prefer to store the thumbnails, encoded videos and other data on the LXC (for the responsiveness and speed), while storing the photos themselves on the NAS. So far this has worked out for me, but keep in mind that if you want to do this, thumbnail and encoded video data do take up space on your LXC disk, so you'll have to make sure you increase your LXC disk size accordingly. You can also customise this to your liking, for example create another symlink for /opt/immich/upload/backups to your bind mount, to store the DB backups on your NAS (I might do this myself).

Steps (Photo files only, as an example)

1. **If you have any existing data in the /opt/immich/upload/upload folder, you better copy/move it to your bind mount location! And make double-certain that your destination has a .immich file (you can simply create an empty one if needed).

2. Delete the /opt/immich/upload/upload dir, leaving the others intact.
   rm -r /opt/immich/upload/upload

3. Create the symlink(s) and restore ownership

ln -sf </media/photoLibrary> (or whatever) /opt/immich/upload/upload
chown -R immich:immich /opt/immich

Looks like this:

root@immich:~# ls -l /opt/immich/upload/
total 11
drwx------ 2 immich immich 17 Jun  9 03:00 backups
drwx------ 3 immich immich  4 May 19 10:16 encoded-video
drwx------ 2 immich immich  3 May 19 09:39 library
drwx------ 3 immich immich  4 May 19 09:53 profile
drwx------ 3 immich immich  4 May 19 09:52 thumbs
lrwxrwxrwx 1 immich immich 20 May 30 16:58 upload -> /media/photoLibrary/

4. Run ./immich-admin change-media-location in /opt/immich/app/bin. See step 6 from above for more info.

OK, that's all folks! If you think anything in this guide can be made more clear and/or explicit, or if you find any errors, please let me know and I will fix 👍🏼

[subtleslander]

Hi there, thanks for the excellent guide! I'm encountering an issue at Step 6:

ERROR [Microservices:StorageService] Failed to read /mnt/immich/encoded-video/.immich: Error: EACCES: permission denied, open '/mnt/immich/encoded-video/.immich'

Any idea on a solution? It doesn't seem to be permissions related, but at the same time the language does suggest as much.

[vhsdream]

@Rakkzi you didn't say whether or not with this reset if the LXC is still privileged or if it's now unprivileged.

If it's unprivileged you'll need to do some work in the LXC conf file with UID/GID mapping. If still privileged, then yes, I think NTFS might be related to the issue.

Do you have any additional mount options set for the share in /etc/pve/storage.cfg? I find these settings useful for me (you'll likely need to adjust):

options uid=1000,gid=2222,file_mode=0660,dir_mode=0775

[Rakkzi]

Sorry, yes, it is privileged. I tinkered around a bit and I'm even more confused now.. I'm able to create, write, and modify files and directories in my new upload location from within the LXC, but the storage service is still telling me permission is denied for the encoded-video .immich. I removed all the .immich files in each directory and used mkdir <backups/uploads/encoded-video/etc> and then touch .immich to recreate them to make sure I could write there, and it made the new files (and folders) just fine. I tried chmod 776 to change permissions on the files/directories, and it appears to have updated them (shows rwxrwxrw now) for the directories but the .immich files themselves are still owned by root and chown immich:immich directly on the .immich file doesn't change them.

root@immich:/opt/immich# ls -l /opt/immich/upload/
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 backups
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 encoded-video
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 library
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 profile
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 thumbs
drwxrwxrw- 2 immich immich 4096 Jul 30 07:05 upload

root@immich:/opt/immich# ls -l /opt/immich/upload/library/.immich
-rwxrwxrw- 1 immich immich 13 Jul 30 07:05 /opt/immich/upload/library/.immich

root@immich:/opt/immich# ls -l /FileServer/upload/.immich
-rwxr-xr-x 1 root root 0 Aug  1 04:21 /FileServer/upload/.immich

root@immich:/opt/immich# chmod -R 776 /FileServer
-rwxr-xr-x 1 root root 0 Aug  1 04:21 /FileServer/upload/.immich

root@immich:/opt/immich# chown -R immich:immich /FileServer
root@immich:/opt/immich# ls -l /FileServer/upload/.immich
-rwxr-xr-x 1 root root 0 Aug  1 04:21 /FileServer/upload/.immich

Using IMMICH_IGNORE_MOUNT_CHECK_ERRORS=true in the .env file stops the error loop and allows me into the webui, but does leave a warning:

[Nest] 397 - 08/01/2025, 5:17:13 AM WARN [Api:ServerInfoRepository~vy02elmb] Failed to read /opt/immich/app/build-lock.json

Trying to import an external library spams the console with:

[Nest] 177  - 08/01/2025, 5:19:48 AM   ERROR [Microservices:{"source":"upload","id":"33f8df0a-482b-48e7-8d1a-6627156eb4fc"}] Unable to run job handler (AssetGenerateThumbnails): Error: EACCES: permission denied, mkdir '/FileServer/thumbs/37d2055f-918c-4cc3-adfa-864e66df30ae/33/f8'
Error: EACCES: permission denied, mkdir '/FileServer/thumbs/37d2055f-918c-4cc3-adfa-864e66df30ae/33/f8'
    at mkdirSync (node:fs:1363:26)
    at StorageRepository.mkdirSync (/opt/immich/app/dist/repositories/storage.repository.js:130:37)
    at StorageCore.ensureFolders (/opt/immich/app/dist/cores/storage.core.js:194:32)
    at MediaService.generateImageThumbnails (/opt/immich/app/dist/services/media.service.js:184:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async MediaService.handleGenerateThumbnails (/opt/immich/app/dist/services/media.service.js:116:25)
    at async JobService.onJobStart (/opt/immich/app/dist/services/job.service.js:198:28)
    at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13)
    at async /opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:499:32
    at async Worker.retryIfFailed (/opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:775:24)

I do not have any extra mount options in storage.cfg, this is how the mount is layed out:

cifs: LocalFileserver
        path /mnt/pve/LocalFileserver
        server 192.168.xxxx
        share <name>
        content rootdir,import,snippets,vztmpl,images,iso
        prune-backups keep-all=1
        username <NTFS Username for share>

[weardj]

@Rakkzi , this is the exact same setup and issues that I'm seeing.

[spocoeric]

Same for me.

[rice1204]

just chiming in to say the same. exactly the same environment (privileged lxc connecting to cifs share), exactly the same error. Verified that I can manually write to the same directory and file. really weird.

Failed to write /mnt/immich/encoded-video/.immich: Error: EACCES: permission denied, open '/mnt/immich/encoded-video/.immich'

Anyone found a cause?

EDIT: crazy enough, it's working correctly now, but I have no idea why. I was messing around with the startup files in /etc/systemd/system/immich-ml.service without success. Finally, i reverted back to the default immich-ml.service, reloaded the startup daemon one last time, and now it's able to write to the CIFS share correctly. The process user remains the same as immich:immich

[fbloemhof]

To complete my migration I also needed to import my database backup. After making my files available using the above how-to (partly) I did the following to restore the database of my Docker setup to the LXC installation.

Warning

Make sure you have backups in place and are working on the correct system etc. No warranty for the steps below.

1. Stop Immich

systemctl stop immich-web immich-ml

2. To make sure I got a fresh start:

# drop the existing database
sudo -u postgres psql -c "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname = 'immich';"
sudo -u postgres psql -c "DROP DATABASE immich;"

# recreate the database with correct collation
sudo -u postgres createdb -O immich --locale=en_US.UTF-8 --template=template0 immich

3. Locate the last backup and restore it:

# set the data location and find the most recent backup
datalocation=/mnt/immich 
latest_backup=$(find $datalocation/backups/ -name 'immich-db-backup-*.sql.gz' -type f -printf '%T@ %p\n' | sort -n | tail -n1 | cut -d' ' -f2-)

# restore the backup
gunzip --stdout $latest_backup \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| sudo -u immich psql --dbname=immich --username=immich

4. Because the LXC script uses other users, we need to change the ownership and the priviliges

# reassing owner and permissions
sudo -u postgres psql -c "
ALTER DATABASE immich OWNER TO immich;
GRANT CONNECT, CREATE ON DATABASE immich TO immich;
REVOKE CONNECT ON DATABASE immich FROM PUBLIC;
"

5. Start Immich and monitor the logfile

systemctl start immich-ml immich-web
tail -f /var/log/immich/web.log

To list the databases and the privileges:

sudo -u postgres psql -c "\l"

I had some minor issues with differences between permissions of the postgres vs immich user, you might need to change that in the commands. Make sure you execute every line one by one to stay in control.

[KatherineTealeaf]

Hi

Thanks a lot for the amazing guide. I notice that when immich is creating files it creates them readable only by the immich user. How do I get it to automatically create the files so that they are readable by the group/all?

[vhsdream]

Hi @KatherineTealeaf - I appreciate the kind words. Normally in Proxmox, especially with an unprivileged LXC, that kind of thing is determined by the host settings.

Can you describe how your storage is configured on your host, primarily these details:

• Original location of storage (directly on Proxmox host, on a NAS, etc)
• Filesystem used (SMB/CIFS, NFS, ZFS, etc)
• How it's mounted in Proxmox (in /etc/fstab, in /etc/pve/storage.cfg, somewhere else)
  • then please provide the configuration details for this.

As an example, I'm storing my photos on a NAS that's running as a VM on Proxmox, with the disks passed through so the VM has control of them. I'm using SMB/CIFS to mount the share on my host, and I used Proxmox's storage UI to configure it. Here is how the entry in my /etc/pve/storage.cfg looks:

cifs: media
        path /mnt/pve/media
        server <ip-address>
        share storage
        content iso
        options uid=1000,gid=2222,file_mode=0660,dir_mode=0775
        prune-backups keep-all=1
        username <whatever>

Important to note is the 'options' part, where I added file_mode and dir_mode settings to ensure that when it's mounted in my LXC, the permissions will be appropriate. In my Immich LXC, files are readable and writable by the user and group as a result.

[jshirle2]

Hello. I am attempting to get this to work with an unpriviliged container (about to give up on that though) and was wondering if you can explain what the options line in this config is doing. Is the Immich user a uid of 1000 on your system? I plan to open immich to the world and as such would rather it be unprivilged but I was not able to find specific documentation that options command and how to properly use it. Thanks!

[vhsdream]

Hi @jshirle2

In my case, these options (especially uid and gid) refer to the UID of my non-root user, and a GID for a group called media I created on my Proxmox host. I'm not 100% sure if using these options is actually necessary, as I did this a couple of years back when I was troubleshooting storage and bind mounts in Proxmox. file_mode and dir_mode make sure that all files and folders have consistent permissions, but again, it might not be necessary.

The way the Immich install script works at the moment is that it creates the immich user as a system user, and as such it ends up having a UID below 1000 in the LXC. There is no real reason why you cannot change the UID and GID of the immich user to suit your requirements. I changed mine to 1000 in the LXC, and also created a media group with a GID of 2222 and added the immich user to the group. This is one part of the modifications needed if you're using an unprivileged LXC.

The other part involves modifying your LXC config file for Immich, as well as 2 other files in your host. Here is the relevant part of my LXC config:

/etc/pve/lxc/124.conf

lxc.idmap: u 0 100000 1000
lxc.idmap: g 0 100000 2222
lxc.idmap: u 1000 1000 1
lxc.idmap: g 2222 2222 1
lxc.idmap: u 1001 101001 64535
lxc.idmap: g 2223 102223 63313

Definitely do not just copy and paste this in your LXC config; but I hope you get the point and can find the correct values for your use-case.

After doing this you need to edit /etc/subuid with the relevant values for you:

root:1000:1
root:100000:65536
chris:165536:65536

And /etc/subgid:

root:2222:1
root:100000:65536
chris:165536:65536

Once the LXC is restarted, then my immich user has read and write access to my bind-mounted CIFS share.

⚠️ A note of caution 💀

Back when I was figuring this out for myself I just went and did this (I think it was for one of the 'Arrs) and suddenly the user was unable to access any of the directories/files besides the share. And even as root in the LXC I couldn't change the permissions. It was a mess.

So before you do this, you should:

• stop all immich services (systemctl disable --now immich-web immich-ml)
• do chown -R root:root /var/log/immich /opt/immich
• change the UID/GID for the immich user/group to what you need it to be
• exit the LXC and do the UID/GID things above (with the correct values for your situation)
• save and reboot the LXC and enter it again
• Then do chown -R immich:immich /var/log/immich /opt/immich
• Then re-enable immich: systemctl enable --now immich-ml immich-web
• Tail the immich-web logs: tail -f /var/log/immich/web.log

Hopefully it works out after that. It might even turn out that because I use the UID 1000 in the mount options ,that's why I have to take those extra steps. I'm not sure and I don't wanna find out!

[wtangofoxtrot]

Running into DB restore issues, anyone else see it ? I followed the above steps to recreate the immich db and get the following when I attempt a restore:

$ gunzip --stdout "/mnt/immich/backups/immich-db-backup-1751156950651.sql.gz" \
| sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
| sudo -u postgres psql --dbname=immich --username=immich
...
COPY 59511
ERROR:  relation "public.face_search" does not exist
...
invalid command \N
invalid command \N
...
ERROR:  syntax error at or near "3038832"
LINE 1: 3038832 Vila 1.56654 42.53176 AD 03  2024-11-04 Encamp
        ^

[vhsdream]

@wtangofoxtrot Is your Immich DB dump that you are attempting to restore from different installation, like a Docker install?

If so, does that Docker install use the same Vector extension? It used to be pgvecto.rs now it's VectorChord (vchord).

[YJCHOO]

@wtangofoxtrot Is your Immich DB dump that you are attempting to restore from different installation, like a Docker install?

If so, does that Docker install use the same Vector extension? It used to be pgvecto.rs now it's VectorChord (vchord).

I encountered the same error, and you were right. After migrating from pgvecto-rs:pg14-v0.2 to postgres:14-vectorchord0.3 and creating a new database dump, I was able to restore it successfully.

I followed this guide for migration.
immich-app/immich#18429

[wtangofoxtrot]

Also pardon my ignorance but where does /opt/immich/app/machine-learning/upload reside in the docker setup that one is migrating from ? The only upload folder I know of is /usr/src/app/upload in the docker setup which maps to /opt/immich/app/upload here however I dont see where /opt/immich/app/machine-learning/upload resides on the docker setup as created using the official compose file https://github.com/immich-app/immich/blob/main/docker/docker-compose.yml

[vhsdream]

@wtangofoxtrot The LXC installation is not a 1:1 of the Immich docker setup. It's cobbled together from a few different sources. I believe that if you do not have the symlink in the machine-learning folder then machine-learning will fail.

[TLauzen]

For your advanced setup wouldn't it make more since to place upload/library on the NAS instead of upload/upload?

[vhsdream]

@TLauzen Nope - that directory is only used if you use the storage template which is not the default option. Mine currently sits empty.

[fbloemhof]

I noticed something yesterday, all my videos from before my migration are not working anymore because their paths are incorrect.

A recent video has /mnt/immich/upload/... as path, while an older video has upload/upload/... as path.

Anyone else noticed this? Would replacing the first 'upload' for the correct path in de DB be enough? hm photos of the same period are also having the same path but are working ok.

[vhsdream]

@fbloemhof It appears that updating to v1.137+ will do the change-media-location automatically, which is good news; but I suppose at the very least it's a good idea to have an immich-admin script that works in case you have to do anything manually.

[fbloemhof]

That sounds even better, will wait until 1.137+ is available then.

[fbloemhof]

Update went well, but the change-media-location did not fix the issue.

The log says TypeError: path must be absolute or specify root to res.sendFile when accessing a video.

[vhsdream]

@fbloemhof Bummer! OK, you should try to do it manually then.

In Immich, try to open a file that results in the error; then click on the little 'i' to see the path:

Now, in your LXC, cd into /opt/immich/app/bin after stopping all Immich services with systemctl stop immich-web immich-ml. Now, if the helper script update did it's job, you should be able to run ./immich-admin change-media-location to get into the interactive script to repair this.

The path from one of those broken videos/images will be the 'previous' IMMICH_MEDIA_LOCATION value; and the current value you have in /opt/immich/env will be the 'new' value. Plug in those paths and then see if the script can do it's work.

After, run this all at once to start Immich and immediately tail the logs:

systemctl start immich-ml immich-web && tail -f /var/log/immich/web.log

Hopefully, this will not show any errors. Let it run in the console and browse around in your collection on the web.

If there are errors, please post them here; today they went from v1.137.0 to 1.137.3 due to edge cases with the media location migration.

I ran the manual commands before they had v1.137.0 out and it worked for me, so there may be an outside chance that the new automatic way it's done in the release is different from what happens if you run the script.

[fbloemhof]

I did some other thing: I did not have a Storage Template configured so I configured this and ran the job (https://immich.app/docs/administration/storage-template/). That fixed it.

In hindsight maybe the change-media-location could have fixed it when I used as the old path upload and new path /upload. Actually, I did this, I am not the only user. Will check later if it fixed it for others. The results of change-media-location look good.

[Lupphes]

Hello,

shouldn't we modify UPLOAD_LOCATION as per https://immich.app/docs/install/environment-variables?

[vsa-d]

(updated 15th Aug.)
Hi...

Thank you very much for this script.

I installed immich again from beginning two days ago.
System: PVE 8.4.6
Method: advanced setup, priveleged lxc., OpenVINO yes
Changes: I used your setup in your post under "advanced setup". I channged uplod/upload und in addition also upload/backup to external usb-HD. I implemented an external libraray (on usb-HD) as read only. Checked all permissions.

root@immich:/# ls -la /opt/immich/
total 40
drwxr-xr-x  9 immich immich 4096 Aug  7 14:26 .
drwxr-xr-x  4 root   root   4096 Aug  3 12:31 ..
drwxr-xr-x  8 immich immich 4096 Aug  3 12:51 app
drwx------  5 immich immich 4096 Aug  3 21:48 .cache
drwxr-xr-x  4 immich immich 4096 Aug  3 21:49 cache
drwx------  3 immich immich 4096 Aug  3 12:52 .config
-rw-r--r--  1 immich immich  451 Aug  7 14:26 .env
drwxr-xr-x  2 immich immich 4096 Aug  3 12:51 geodata
lrwxrwxrwx  1 immich immich   25 Aug  3 12:50 resources -> /opt/immich/app/resources
drwxr-xr-x 20 immich immich 4096 Aug  3 12:31 source
drwxr-xr-x  6 immich immich 4096 Aug  3 20:31 upload

root@immich:/# ls -la /opt/immich/upload/

drwxr-xr-x 6 immich immich 4096 Aug  3 20:31 .
drwxr-xr-x 9 immich immich 4096 Aug  7 14:26 ..
lrwxrwxrwx 1 immich immich   19 Aug  3 20:31 backups -> /mnt/immich_backups
drwx------ 3 immich immich 4096 Aug  4 10:50 encoded-video
drwx------ 2 immich immich 4096 Aug  3 12:52 library
drwx------ 2 immich immich 4096 Aug  3 12:52 profile
drwx------ 5 immich immich 4096 Aug  7 14:30 thumbs
lrwxrwxrwx 1 immich immich   18 Aug  3 20:30 upload -> /mnt/immich_upload

Setting in immich I made: Changes in Quality of thumbmails (lower quality); Turned on Reading Metadata of Faces in EXIF (because I have lots of pictures where faces are already tagged correctly); hardware acceleration - turned on from "none" to VAAPI

Everything looks like above and seems to work fine. I can see all the pictures and videos, VAAPI works with trancoding all the videos and even the already given face-tags are there.

But I get many errors like this

tail -f /var/log/immich/web.log , I think because of AI(?)

[Nest] 177  - 08/15/2025, 3:17:07 PM    WARN [Microservices:MachineLearningRepository] Machine learning request to "http://127.0.0.1:3003" failed with status 500: Internal Server Error
[Nest] 177  - 08/15/2025, 3:17:07 PM   ERROR [Microservices:{"source":"upload","id":"b54ed13f-e557-4eb7-a9a9-e2df7a9be502"}] Unable to run job handler (AssetDetectFaces): Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs
Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs
    at MachineLearningRepository.predict (/opt/immich/app/dist/repositories/machine-learning.repository.js:98:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async MachineLearningRepository.detectFaces (/opt/immich/app/dist/repositories/machine-learning.repository.js:107:26)
    at async PersonService.handleDetectFaces (/opt/immich/app/dist/services/person.service.js:240:52)
    at async JobService.onJobStart (/opt/immich/app/dist/services/job.service.js:198:28)
    at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13)
    at async /opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:499:32
    at async Worker.retryIfFailed (/opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:775:24)
[Nest] 177  - 08/15/2025, 3:17:07 PM   ERROR [Microservices:{"source":"upload","id":"b54ed13f-e557-4eb7-a9a9-e2df7a9be502"}] Unable to run job handler (SmartSearch): Error: Machine learning request '{"clip":{"visual":{"modelName":"ViT-B-32__openai"}}}' failed for all URLs
Error: Machine learning request '{"clip":{"visual":{"modelName":"ViT-B-32__openai"}}}' failed for all URLs
    at MachineLearningRepository.predict (/opt/immich/app/dist/repositories/machine-learning.repository.js:98:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async MachineLearningRepository.encodeImage (/opt/immich/app/dist/repositories/machine-learning.repository.js:116:26)
    at async SmartInfoService.handleEncodeClip (/opt/immich/app/dist/services/smart-info.service.js:91:27)
    at async JobService.onJobStart (/opt/immich/app/dist/services/job.service.js:198:28)
    at async EventRepository.onEvent (/opt/immich/app/dist/repositories/event.repository.js:126:13)
    at async /opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:499:32
    at async Worker.retryIfFailed (/opt/immich/app/node_modules/bullmq/dist/cjs/classes/worker.js:775:24)
[Nest] 177  - 08/15/2025, 3:27:12 PM     LOG [Microservices:MediaService] Successfully encoded b077b2f5-8bf8-4c6b-9d0a-8c6998441571
[Nest] 177  - 08/15/2025, 3:28:16 PM     LOG [Microservices:MediaService] Transcoding video 6fc257ba-d5e6-4dbb-a2ad-b5a265e11d0c with VAAPI-accelerated encoding and software decoding

GPU is passing through. (Dell Wyse 5070 with Intel J5005, immich priv. lxc with 6GB ans 1GB SWAP) OpenVINO seems to work (see log above)

I put that into the ..../lxc/120.conf on host:

lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file
lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.mount.entry: /dev/dri/card0 dev/dri/card0 none bind,optional,create=file
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir

Noone else with those errors in the log?

[vsa-d]

(updated 15th Aug).

I tried it also in a clean install with adding that line in .env:

IMMICH_MACHINE_LEARNING_PROVIDER=onnx

and restartet immich. Unfortunately I still got theese errors. :-(

I removed the line.

[vsa-d]

Just a few logs, hopefully that someone understands what that could be?

root@immich-server:~# tail -f /var/log/immich/ml.log 
[08/15/25 15:22:12] INFO     Application shutdown complete.                     
[08/15/25 15:22:12] INFO     Finished server process [372]                      
[08/15/25 15:22:13] ERROR    Worker (pid:372) was sent SIGINT!                  
[08/15/25 15:22:13] INFO     Booting worker with pid: 44305                     
[08/15/25 15:22:26] INFO     Started server process [44305]                     
[08/15/25 15:22:26] INFO     Waiting for application startup.                   
[08/15/25 15:22:26] INFO     Created in-memory cache with unloading after 300s  
                             of inactivity.                                     
[08/15/25 15:22:26] INFO     Initialized request thread pool with 3 threads.    
[08/15/25 15:22:26] INFO     Application startup complete.        

and web.log (just two lines, the other lines are same like in my first post above):
Error: Machine learning request '{"facial-recognition":{"detection":{"modelName":"buffalo_l","options":{"minScore":0.7}},"recognition":{"modelName":"buffalo_l"}}}' failed for all URLs
and
Error: Machine learning request '{"clip":{"visual":{"modelName":"ViT-B-32__openai"}}}' failed for all URLs

Something wrong with face recognition.
Like I already told above, I didn't change anything in the settings, just the setting to read already tagged faces in exif. I only use my external library.

So...could this be a bug in the script? Could kindly some check the own weblog if there are those errors (with persons on your photos) while importing new data, please?

[vsa-d]

Hello @vhsdream

Immich ml Webserver is started as it should (checked 127.0.0.1:3003)
Still the Errors when I import Photos with faces.
I also updated (sccessfully with "update" to 1.138)

I think it must be a bug in the script. Could it be that the AI models ViT-B-32__openai and bufalo_l are not installed?
Thanks in advance for checking it.

[vhsdream]

@vsa-d It's not a problem with the script, it looks like a problem with your machine-learning configuration. As for the models, Immich downloads them automatically when it starts a machine-learning operation. Check /opt/immich/cache to see if there are models there, delete them if so - perhaps the download was interrupted.

There's also a chance that your Intel iGPU just cannot handle hardware acceleration, but normally what happens is that it falls back to CPU only, and maybe your CPU is having trouble with that.

You can also go into your settings again and increase the loggin verbosity to see if there is more output that we can use to diagnose the issue.

[vsa-d]

Thnak you very much for support.
I checked logs with more information, but there were the same errors like posted. So I decided to deinstall the OpenVINO and changed lanst line in ml_start.sh with python3 -m immich_ml --extra cpu --no-cache --active

Now it seems to work... Probably my intel J5005 is not able to work with OpenVINO in Proxmox Containers, although I decided to make it privileged.

[etrigan63]

I am a bit confused as to what to do here. I have an unprivileged LXC container running immich. I have an NFS share on my truenas server where I want the data to live. I have mounted the NFS share on my PVE host using the gui. I have bound said mounted share to my container using the pct set command. The mounted share always has an images folder and is permanently owned by nobody/nogroup. I am quite stuck.

[Ingraved]

Unpriviliged LXCs are weird. You have to treat 'root' as a normal user with bind mounts.
What I recommend is to find the ID of the immich user inside the lxc with id immich then in the host you need to chown -R 100999:100000 /mnt/immich This will make the owner immich and the group root inside the LXC. Then make sure to chmod -r 770 /mnt/immich

[etrigan63]

Bingo! That got it! You may want to streamline the steps to reflect this.

[Ingraved]

I asked my document expert friend Chet G. Petey to beautify my steps on how to fix the permissions:

---

📸 Immich Bind Mount Permissions for Unprivileged LXC on Proxmox

This guide explains how to set correct permissions on a bind-mounted media directory (e.g., /mnt/immich) for an unprivileged LXC container running Immich on Proxmox.

---

✅ Prerequisites & Assumptions

• 🐧 Immich installed via community scripts
  → https://community-scripts.github.io/ProxmoxVE/scripts?id=immich

• 🆔 Immich LXC container ID: 200

• 📁 Bind mount is already configured in container config:

  mp0: /mnt/immich,mp=/mnt/immich

• 👤 immich user inside the container has UID: 999

• 🛑 Immich is currently stopped:

  systemctl stop immich-web immich-ml

• 🧰 You've completed Steps 1–6 from:
  ⚙ Changing the Immich upload directory in your Immich LXC

⚠️ Adjust the values above to match your own environment.

---

🛠️ Steps

1. Confirm Immich user UID inside the LXC

Run this on the Proxmox host:

pct exec 200 -- id immich

You should see something like: uid=999(immich) gid=996(immich)
The UID is 999, and maps to 100999 on the host (for unprivileged LXC).

---

2. Set ownership of the bind mount on the host

Still on the Proxmox host:

chown -R 100999:100000 /mnt/immich

This assigns ownership to the immich user (UID 999) inside the container.

---

3. Set access permissions for group and user

chmod -R 770 /mnt/immich

This gives read/write/execute to both the immich user and unprivileged root' group on the host 'owned' /mnt/immich`.

---

4. Resume Immich setup

Return to Step 7 in:
⚙ Changing the Immich upload directory in your Immich LXC

---

✅ Notes

• The UID/GID mappings are based on root:100000:65536 in /etc/subuid.
• UID 999 inside the container maps to UID 100999 on the host.
• chmod 770 ensures root in the container can also access the files.

---

Hopefully, my friend Chet is okay to use. 😄

[Lupphes]

This worked for me

[weardj]

I'm still running into the same issue.

ERROR [Microservices:StorageService] Failed to write /mnt/Photos/encoded-video/.immich: Error: EACCES: permission denied, open '/mnt/Photos/encoded-video/.immich'

On the Proxmox host, my immich users match up exactly as you have, 999. My mount is mp0: /mnt/pve/Photos,mp=/mnt/Photos. I noticed when I "chown -R 100999:100000 /mnt/pve/Photos", it doesn't seem to change. Doing ls -l /mnt/pve shows the /Photos as 100000. Within the immich LXC, /mnt/photo is owned by root.

root can touch the folder and create files, but it seems like immich cannot.

[Lupphes]

I have it currently like this

root@pve-nugget:~# ls -la /mnt/pve/immich/
total 41
drwxrwx--- 10 100999 100000   10 Aug  3 19:12 .
drwxr-xr-x  7 root   root   4096 Jul 27 21:20 ..
drwxrwx---  2 100999 100000    8 Aug  8 02:00 backups
drwxrwx---  2 100999 100000    2 Aug  3 19:11 dump
drwxrwx---  3 100999 100000    4 Aug  3 20:28 encoded-video
drwxrwx---  3 100999 100000    4 Aug  3 19:16 library
drwxrwx---  2 100999 100000    2 Aug  3 19:11 private
drwxrwx---  2 100999 100000    3 Aug  3 18:02 profile
drwxrwx---  3 100999 100000    4 Aug  3 19:16 thumbs
drwxrwx---  3 100999 100000    4 Aug  3 19:16 upload

root@pve-nugget:~# ls -la /mnt/pve/
total 59
drwxr-xr-x  7 root   root   4096 Jul 27 21:20 .
drwxr-xr-x  5 root   root   4096 Jul 27 21:14 ..
drwx--s--- 15 root   root     22 Aug  7 01:21 backup
drwxrwx--- 10 100999 100000   10 Aug  3 19:12 immich

[weardj]

I think I figured it out. I'm mounting a share that exists on windows so chown wouldn't update the ownership. I had to remount with the correct ownership, matching up to the immich user id.

mount -t cifs -o user=<Share Username>,uid=100999,gid=100996 //<FileServer>/Photos /mnt/pve/Photos

[gericho]

I still have an issue with an NFS export configured with no_root_squash, Privileged container. I am migrating a previous SMB media folder, the current NFS is mounted directly in the guest to /mnt/photos with nfs-common. On the host, all the files are owned by root:media. I have recreated the same media group GID (1000) on the Immich server and added immich to it, but I am still getting this error.

[Nest] 658  - 08/13/2025, 8:17:17 PM   ERROR [Microservices:StorageService] Failed to read (/mnt/photos/encoded-video/.immich): Error: EACCES: permission denied, open '/mnt/photos/encoded-video/.immich'
microservices worker error: Error: Failed to read: "<UPLOAD_LOCATION>/encoded-video/.immich (/mnt/photos/encoded-video/.immich) - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information.", stack: Error: Failed to read: "<UPLOAD_LOCATION>/encoded-video/.immich (/mnt/photos/encoded-video/.immich) - Please see https://immich.app/docs/administration/system-integrity#folder-checks for more information."
    at StorageService.verifyReadAccess (/opt/immich/app/dist/services/storage.service.js:127:19)
    at async /opt/immich/app/dist/services/storage.service.js:56:21
    at async /opt/immich/app/dist/repositories/database.repository.js:379:27
    at async /opt/immich/app/node_modules/kysely/dist/cjs/kysely.js:535:20
    at async DefaultConnectionProvider.provideConnection (/opt/immich/app/node_modules/kysely/dist/cjs/driver/default-connection-provider.js:12:20)
    at async /opt/immich/app/dist/repositories/database.repository.js:376:13
microservices worker exited with code 1
Killing api process

root@immich:~# ls -l /mnt/photos/
total 28
drwxrwx--- 2 root media 4096 Aug 13 02:00 backups
drwxrwxrwx 3 root media 4096 Aug 13 19:37 encoded-video
drwxrwx--- 2 root media 4096 Jun 17 16:59 library
drwxrwx--- 4 root media 4096 Jun 17 17:09 ml_cache
drwxrwx--- 3 root media 4096 Jun 17 17:29 profile
drwxrwx--- 3 root media 4096 Jun 17 17:08 thumbs
drwxrwx--- 3 root media 4096 Jun 17 17:07 upload
root@immich:~# 

root@immich:~# id immich
uid=999(immich) gid=996(immich) groups=996(immich),44(video),104(render),1000(media)

I have already tried recursively changing the ownership of all directories on the NFS server to UID:GID 999:996. After doing this, the web UI works, but the collection is not visible, it's empty.
I am migrating all my shares to NFS, so keeping an SMB share only for Immich is not feasible.
Thank you in advance!

[etrigan63]

On the NFS Share you have to add mapall set to root. On the Proxmox host you have to chown the mounted share to 100xxx and 100000 where xxx is the UID used inside the LXC container. That is how I got mine to work. This assumes an unprivileged container, Proxmox host mounting the share, and mapping the local version of the mount to the LXC via pct set command.

[gericho]

Thank you for your reply. Unfortunately, I need to use a privileged LXC in order to utilise OpenVINO machine learning acceleration.

[etrigan63]

I would still do the mapall on the share and then enable NFS in the container and mount the share directly inside the container. Leave the NFS share owned by root:root and do the chmod -R 770. Mapall should handle converting immich:root inside the container to root:root on the NFS server.

[shahzebz]

This script has been a life saver! Thank you for the amazing guide!

[pafftis]

I installed immich using a script. Can you tell me the password for the root user? I need to log in using ssh.

[shahzebz]

I believe if you installed using a helper script you don't have to enter a password to login, it should login to the console directly. Open the console via Proxmox Browser UI and then you can reset password

[Aaron-K]

Thank you for the great guide! I'm running into an upload utime issue with Immich, the unprivileged Proxmox LXC Container, and the SMB nas share. I have a different setup following the fstab method here: Tutorial: Unprivileged LXCs - Mount CIFS shares.

The error I'm getting is:
[Nest] 369 - 08/16/2025, 8:59:13 PM ERROR [Api:AssetMediaService~hy1tbhak] Error uploading file Error: EPERM: operation not permitted, utime '/mnt/nas/immich/upload/2014e5da-27a1-4bde-ab34-90010d1868ba/4c/d4/4cd4e992-ee8d-4c5a-8984-631d50d57299.JPG'
Which seems related to a permission issue, but I moved and added the files in this guide to the /mnt/nas and I can touch/add files to each directory using root and the Immich user. Immich can also add all the sub-folders it needs when trying to upload. The Immich web app can see the correct storage on the /mnt/nas as well.

Anyone else getting this error? Hitting a wall here, and not really sure what's wrong. I may move on to trying an NFS Share instead.

[vhsdream]

@Aaron-K I think you're right about a permission issue, but this time it seems specifically related to file modification permissions.

Can you share the contents of /etc/fstab from your host (minus the credentials)? Or tell me what UID and GID you mounted the share as.

If you haven't already, try using relatime or lazytime instead of noatime - that might be what is causing the error.

[Aaron-K]

Sure @vhsdream:

 GNU nano 7.2                                          /etc/fstab                                                   
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=uuid-number /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

# Mount CIFS share on demand with rwx permissions for use in LXCs 
//nas-ip/data/ /mnt/lxc_shares/nas_rwx cifs _netdev,x-systemd.automount,noatime,uid=100000,gid=110000,dir_mode=0770,file_mode=0770,user=nasuser,pass=naspassword 0 0

Both root and immich are part of the lxc_shares user group.

Thank you for the help. I tried both relatime and lazytime rather than noatime and unfortunately no change. The SMB share is on Unraid. Maybe a fuse issue with Unraid? Just starting to learn with Proxmox and Unraid.

I did stumble upon this post on the immich git repo. I tried the change suggested by denysvitali which did allow the upload to work. I feel like this is a workaround or bandaid rather than a fix, but wanted to provide it for context.
My steps were:

• Create new .js file called fs-patch.js with the JS that denysvitali wrote. Place the file in /opt/immich/patch/fs-patch.js
• Edit the immich-web.service file with systemctl edit immich-web.service
• Added this to immich-web.service:

[Service]
Environment="NODE_OPTIONS=--require /opt/immich/patch/fs-patch.js"

This is allowing me to upload at the moment, but as stated before, seems like I'm just bypassing the issue and I'm not sure if I'm creating any future issues for myself with Immich.

[vhsdream]

@Aaron-K maybe the immich user needs to own the folder instead of root. For example this is what my folder structure looks like:

root@immich:~# ls -la /media/photoLibrary/
total 9
drwxrwxr-x 2 immich media  0 Jun 29 21:17 .
drwxr-xr-x 3 root   root   3 May 24 13:12 ..
drwxrwxr-x 2 immich media  0 May 20 18:18 f3fc48cd-bdde-4b88-987e-83aec8f4fd2f
-rw-rw---- 1 immich media 13 Aug 15 08:01 .immich

I achieved this by using custom mount options in /etc/storage.cfg to mount the share with the UID 1000, and then used UID mapping in the LXC config file.

To do that in your situation might require a lot of work, if you are also using the share with other LXCs. I suppose you would need to change the UID of every user in each LXC that needs access to the share to the same UID.

But it's also a possibility that Immich simply does not support non-POSIX filesystems; and that something with the way an SMB share is mounted via fstab interferes with it in a way that using /etc/pve/storage.cfg does not.

[Aaron-K]

@vhsdream I may give that a try. Thank you for that recommendation. I'm in the early setup phase of everything, so now would probably be the time. It may take me some time and error, so I'll follow up with the results if I get a chance to go that route. I don't want to take up your guide comments with this issue more than I have too, but thanks again for the support!

[madcar86]

i did this and it seemed to delete all my media from the previous immich server. Is there any way to get it back, or is it gone?

[vhsdream]

Changing the upload directory wouldn't delete a library. You'll need to restore from a backup or keep troubleshooting your configuration.

You have backups, right?

[MickLesk]

@vhsdream you are Not in discord, so i need to random ping you in some Discussions. Immich switched to pnpm

immich-app/immich#21113

[vhsdream]

@MickLesk no worries, I'm well aware and I've been working on it the past couple of days 😄

[rh8056]

I just went through the process of trying to move my media location. I read through those steps a few times, then went step by step, very carefully, but when I restart the services and tail the log, I see this error:

at async /opt/immich/app/dist/repositories/database.repository.js:376:13
microservices worker error: Error: Detected an inconsistent media location. For more information, see https://immich.app/errors#inconsistent-media-location, stack: **Error: Detected an inconsistent media location**. For more information, see https://immich.app/errors#inconsistent-media-location

I rechecked everything. My .env file has:

IMMICH_MEDIA_LOCATION=/mnt/immich

When I run change-media-location I see the right thing in the examples from the database:

  Examples from the database:
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/eb/15/eb155747-5e03-4a26-a44f-3eb765ad8673.jpeg
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/48/b5/48b55ffb-e402-49b8-b5c4-cda724fd1b09.jpeg
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/aa/c4/aac41664-061e-41f7-ab23-f2f9880f229d.jpeg
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/40/56/4056490c-65c5-4c77-a6e3-80349f9ee280-preview.jpeg
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/40/56/4056490c-65c5-4c77-a6e3-80349f9ee280-thumbnail.webp
  - /mnt/immich/thumbs/29c78208-ca0a-42c4-a0b5-a8fb53fb7c2c/7d/ea/7dea153c-079f-4244-b4f1-147d35e7b84b-preview.jpeg

When I check the two symlinks, they seem correct:

# ls -all /opt/immich/app/upload
lrwxrwxrwx 1 root root 11 Sep  9 13:55 /opt/immich/app/upload -> /mnt/immich
# ls -all /opt/immich/app/machine-learning/upload
lrwxrwxrwx 1 root root 11 Sep  9 13:56 /opt/immich/app/machine-learning/upload -> /mnt/immich
# 

Ideas on what else I should check? I tried adding UPLOAD_LOCATION to the .env file, and then restart the LXC, but still getting the same error in the log.

[rh8056]

I reset everything to the old locations (undoing what I had done) and verified all was working correctly. I then walked through the guide again and did not do the change-media-location script at all. This seems to have been the problem. I saw the comment when doing it the first time and interpreted:

ANOTHER UPDATE - literally as I posted the above, a new version dropped which apparently will detect a change to IMMICH_MEDIA_LOCATION and will do the above for you automatically.

to mean that it was optional, not that it should be skipped post 1.137.

[vhsdream]

@rh8056 I'm sorry for the trouble! Due to there being too many variables at the time, I was not able to confirm if it was still necessary to run that script. I guess it isn't anymore, so I will update the post to indicate that it is entirely optional and perhaps no longer necessary.

[rh8056]

No real trouble at all. It's all a learning experience and this guide is quite helpful!

In my case, running that script seemed to mess it up, but I'm not sure why. So a notice at the beginning of step 6 that it can/ should be skipped, could be helpful.