Unable to update immich, Portainer access is limited
docker cpmpose config
root@openmediavault:/srv/dev-disk-by-uuid-d2c58590-93d7-4346-af7a-5c7856a3738f/docker/volumes/portainer_data/_data/compose/2# docker-compose config WARN[0000] The "UPLOAD_LOCATION" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_PASSWORD" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_USERNAME" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_DATABASE_NAME" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string. invalid spec: :/var/lib/postgresql/data: empty section between colons
215 Replies
:wave: Hey @RolloMollo,
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_01GY0DAKGXDEHE263BCAYEGFJAChecklist
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.GitHub
immich-app immich Β· Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues Β· immich-app/immich
High performance self-hosted photo and video management solution. - Issues Β· immich-app/immich
Portainer uses
stack.env
instead of .env
. Is that file there in the same folder?Gimmie a second
quite new to discord
sorry
stack env
UPLOAD_LOCATION=/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/pictures
DB_DATA_LOCATION=/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/docker_data
IMMICH_VERSION=release
DB_PASSWORD=XXXX
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
You set them in the Portainer UI under the compose section. It's not a file on the sytem you create as an FYI
compose file
You are right. Set this up in portainer under stacks
now i have limited access (updated portainer)
I can aceesss immich and upload files but i am not able to update the image/immich
tried it via CLI but then I got the message above
I also saw the release notes here
https://github.com/immich-app/immich/releases/tag/v1.102.0
But now i dont know how to fix the bug and updat the container / or get portainer running again
What version were you coming from? That's quite far back
1.124.2
Coming from, not the latest version. You only need to read the breaking changes between what version you were on and what version you were jumping too
yes thanks
Should i repleace env only with
+DB_DATA_LOCATION=./postgres
Were you using a docker volume before?
now its getting complicated. I installed portainer in the past (however i did this) on open media vault (installed on proxmox).
Then i updated portainer through open media vault GUI
now I am not sure how I instaled it

Well this may be hard to diagnose if you are unsure of the steps in between, you should see if you have the postgres data anywhere on the file system
yes
so far i already copied them via this command
c
p -r /srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/docker_data /srv/postgres_data
but now i am unsure what to do next

I also know the password for the database
thanks for you help by the way
Maybe i update stack env with
DB_DATA_LOCATION=/srv/postgres_dataWhat do you think?
I would try that yes, set the DB Location to where you have the DB data in the FS
ok no changes to compose nedded right?
Because everything is at stack env
Correct
Same message:
docker-compose config
WARN[0000] The "DB_DATA_LOCATION" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_DATABASE_NAME" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_PASSWORD" variable is not set. Defaulting to a blank string. WARN[0000] The "DB_USERNAME" variable is not set. Defaulting to a blank string. WARN[0000] The "UPLOAD_LOCATION" variable is not set. Defaulting to a blank string. invalid spec: :/var/lib/postgresql/data: empty section between colonsstack
UPLOAD_LOCATION=/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/pict> DB_DATA_LOCATION=/srv/postgres_data IMMICH_VERSION=release DB_PASSWORD=sdfioq3r89c809asd/&&/()sdfs! DB_USERNAME=postgres DB_DATABASE_NAME=immichdring me crazy π¦
Maybe has to do you with originally not using portainer for the setup? I am not sure in that case. It should just pull from the stack.env
yeah you are right
in the beginning it was setup with a different instance of portainer (stack)
Now i try to update it via cli / docker
realy freeking out to get it fixed or set it up again w/o losing data
if you're using CLI the file must be called .env
stack.env is a portainer ONLY oddity
uh good omne
*one
let me check

Cant see it any more!?
ok found it (invisible)
Ok with docker config i am getting back the compose file
which is new and sounds great so far!?
how is it possible to update now immich?
can someone help me?
I tried this commaned but it didnt work
root@openmediavault:/srv/dev-disk-by-uuid-d2c58590-93d7-4346-af7a-5c7856a3738f/docker/volumes/portainer_data/_data/compose/2# docker pull immich-server Using default tag: latest Error response from daemon: pull access denied for immich-server, repository does not exist or may require 'docker login': denied: requested access to the resource is denieddocker-compose pull is working
don't use
docker-compose

used this commands
but now i am getting this

looks unhealthy

:KEKL:
any help appreciated
seems to be a bootloop or whatever

Whatβs the filesystem of your Postgres data
how to identify that?
I mean you would have set it up right?
yes i had
used the process https://immich.app/docs/install/portainer/
or do you mean the filesystem of open media vault?
then its ext4
mm
Noone that saw that he still has 3001:2883?
I don't see any changes from stock compose @RolloMollo so you're probably best off downloading the newest one, changing .env to stack.env and then restarting the stack
Should you ever want to use the CLI when using portainer, you'll just need to specify the env file like so:
docker compose --env-file stack.env whatevercommand
will do asap
need to get the kids to bed
For clarification, I mean env to stack.env in the compose file, not download the newest env
do i need to use docker compose or just stop, pull, start?
thanks for clarify
same errors again π¦

And if you do
docker compose logs immich_postgres
no such service: immich_postgres
my bad,
docker compose --env-file stack.env logs database
seems that postgress is always restarting
Well yes, but why
just to clarify
i didnt touch the ".env" file
Sounds good to me! π
just downloaded the newest compose file
docker compose --env-file .env logs database
Wait did you mv the stack.env to .env and never move it back?
corrct :/
correct
yeah you should move that back to stack.env π
wait a second
and compose down etc
(and also use portainer probably)
ah ok
so now i have to files: compose (nedd to add "srtack.env" and stack.env
now i set it up again in my new portainer session
right?
wait a second π let's clarify
ok
you were using the default compose, with ".env" inside?
Or did you replace it with stack.env
I downloaded the default compose file, edit nothing (default). In the same folder I got my "old" .env file including my "old settings"
then i run compose down, comose up -d
Right, that was the good way actually π only not if you wanted to manage through portainer but that's besides the point of course
so tbh i dont care about portainer
What did this output?
i just wanted to get it running up again with the latest version
(don't need hte --env-file it you're using .env)
so now i renemad it to stack.env
one sec rename it to .env again
I used now
docker compose --env-file stack.env logs database
correct? only using .env file (not stack.env)
you don't need the --env-file stack.env if its named .env
that's just because portainer is weird and names it stack.env
docker compose logs database
yes
wait need to fire it up again
it repeats:
immich_postgres | Data page checksums are enabled.
immich_postgres |
immich_postgres | initdb: error: directory "/var/lib/postgresql/data" exists but is not empty
immich_postgres | If you want to create a new database system, either remove or empty
immich_postgres | the directory "/var/lib/postgresql/data" or run initdb
immich_postgres | with an argument other than "/var/lib/postgresql/data".
immich_postgres | The files belonging to this database system will be owned by user "postgres".
immich_postgres | This user must also own the server process.
immich_postgres |
immich_postgres | The database cluster will be initialized with locale "en_US.utf8".
immich_postgres | The default database encoding has accordingly been set to "UTF8".
immich_postgres | The default text search configuration will be set to "english".
That's it? π

thats it
i mean the same and same over and over again

What you'd like to see is:
immich_postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization
would love to see this π
really not great in all the docker stuff (yes I know, and you are using immich ) but can it be linked to the folder which were mounted by docker or something like this?
like folder access
or something like this
I was just checking but the folder
DB_DATA_LOCATION
is mounted in the container to /var/lib/postgresql/data/
So the question is, what exactly is inside DB_DATA_LOCATION
and why does it not recognize it as a DBi can check it via CLI?
I'm spying
You shouldn't do -r, you should do -a
ok
i can do it again
but
/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/docker_data
was DB_DATA_LOCATION
?correct
Alright π
-a will preserve permissions
which is likely what is going wrong here
ok
compose down
copy it again with -a
compose up
right?
yep
nope restarting again
Does the logs command still say the same?
on it
(btw the important logs are written to the db folder)

yeah that was going to be my next question π
Woops, sorry π
hurray that's progress
now check the DB_DATA_LOCATION, inside it is a logs folder with more logs
ok

i think the last one
Definitely
2025-01-16 18:22:35.013 UTC [1] LOG: starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-01-16 18:22:35.013 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-01-16 18:22:35.013 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-01-16 18:22:35.030 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-01-16 18:22:35.054 UTC [27] LOG: database system was shut down at 2024-07-25 11:54:00 UTC
2025-01-16 18:22:35.054 UTC [27] LOG: record with incorrect prev-link 66A2/1C5B0000 at 1/9CF99758
2025-01-16 18:22:35.054 UTC [27] LOG: invalid primary checkpoint record
2025-01-16 18:22:35.054 UTC [27] PANIC: could not locate a valid checkpoint record
[2025-01-16T18:22:35Z INFO service::utils::clean] Find directory "pg_vectors/indexes/109799".
[2025-01-16T18:22:35Z INFO service::utils::clean] Find directory "pg_vectors/indexes/17331".
[2025-01-16T18:22:35Z INFO service::utils::clean] Find directory "pg_vectors/indexes/17331/segments/1407e07a-5dbf-4bde-90e2-e7cb75f0ff38".
[2025-01-16T18:22:35Z INFO service::utils::clean] Find directory "pg_vectors/indexes/109799/segments/1d517a68-8108-4207-a3ad-f41a76822d49".
2025-01-16 18:22:36.323 UTC [38] FATAL: the database system is starting up
2025-01-16 18:22:36.324 UTC [39] FATAL: the database system is starting up
2025-01-16 18:22:37.701 UTC [1] LOG: startup process (PID 27) was terminated by signal 6: Aborted
2025-01-16 18:22:37.701 UTC [1] LOG: aborting startup due to startup process failure
2025-01-16 18:22:37.716 UTC [1] LOG: database system is shut down
database system was shut down at 2024-07-25 11:54:00 UTCUh what π Is that the very latest? Because it says 18:22 and the last attempt was 18:29
hm
i can delete any log right now
compose down compose up
and then check again
Sure, it's all copied anyway π
ah
wait a sec
my mistake
thin this is the latest one
2025-01-16 19:31:10.016 UTC [1] LOG: starting PostgreSQL 14.10 (Debian 14.10-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2025-01-16 19:31:10.016 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2025-01-16 19:31:10.016 UTC [1] LOG: listening on IPv6 address "::", port 5432 2025-01-16 19:31:10.022 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2025-01-16 19:31:10.030 UTC [28] LOG: database system was shut down at 2024-07-25 11:54:00 UTC 2025-01-16 19:31:10.030 UTC [28] LOG: record with incorrect prev-link 66A2/1C5B0000 at 1/9CF99758 2025-01-16 19:31:10.030 UTC [28] LOG: invalid primary checkpoint record 2025-01-16 19:31:10.030 UTC [28] PANIC: could not locate a valid checkpoint record [2025-01-16T19:31:10Z INFO service::utils::clean] Find directory "pg_vectors/indexes/109799". [2025-01-16T19:31:10Z INFO service::utils::clean] Find directory "pg_vectors/indexes/17331". [2025-01-16T19:31:10Z INFO service::utils::clean] Find directory "pg_vectors/indexes/17331/segments/1407e07a-5dbf-4bde-90e2-e7cb75f0ff38". [2025-01-16T19:31:10Z INFO service::utils::clean] Find directory "pg_vectors/indexes/109799/segments/1d517a68-8108-4207-a3ad-f41a76822d49". 2025-01-16 19:31:10.056 UTC [33] FATAL: the database system is starting up 2025-01-16 19:31:10.601 UTC [40] FATAL: the database system is starting up 2025-01-16 19:31:12.874 UTC [1] LOG: startup process (PID 28) was terminated by signal 6: Aborted 2025-01-16 19:31:12.874 UTC [1] LOG: aborting startup due to startup process failure 2025-01-16 19:31:12.877 UTC [1] LOG: database system is shut down
Corrupt DB? π
yeah seems like it
this doesnt sound good
anything in UPLOAD_LOCATION/backups ? π
seems to be
mounting the folder in mac os



filled with pictures
immich was running fine. after compose down and pull and up I have now a broken DB π¦
I was specifically asking about UPLOAD_LOCATION/backups but yeah
Let's see uh
temporarily disable the DB healtcheck by commenting it out in the compose file, that's these lines:
Just preface them all with a #, taking care not to break indentation
(first compose down)
then start the DB container only:
docker start immich_postgres
Next docker exec -it immich_postgres /bin/bash
ok
switch to postgres user
su postgres
and reset the WAL log pg_resetwal /var/lib/postgresql/data
exit the container with exit and do docker compose up -d
to see if it's alivedocker start immich_postgres
Error response from daemon: No such container: immich_postgres
Error: failed to start containers: immich_postgres
First compose up?
uh sorry, first
docker compose create
yaml: line 65: did not find expected '-' indicator
need to check the yaml
Don't forget to comment
ahhh
thanks
thank very much for your time!
worked
Yeah now the start and the whole shebang
on it
not that easy because its rebooting the whole time
is it possible to sum it up in one command?
It's not supposed to be rebooting with the healtcheck disabled π€
uh
not a good sign
Ugh it's going to be
Isn't it π₯²
ok
Need to run the compose create after every compose.yaml edit
uhhh
so now i edit compose again
set healtcheck to true (mean disable)
I leave the "#"?
same
restarting over and over again

dont if its a good idea but omv is set up on proxmox. I can restore a backup of the whole VM
maybe I get immich running again!?
Good/bad idea?
That could work, how recent is the backup?
5.01.2025
12.01.2025
didnt make any chances to my files
and oicturess are saved on the phones as well
Anything else running on OMV?
not realy
You could also re-upload to a new immich instance from where they are now, it willmean losing all the metadata like user accounts, face grouping etc though
I mean the main problem will maybe stay because DB was saved on an external drive. And as far as I know Proxmox is just backuping up the VM but not the external drive
mhhh also a great idea
In this case the pictures are not lost right?
Yes, but with a caveat
you can't upload and keep them where they are, it will duplicate them
like old_upload -> new_upload locations will duplicate the pics
what would you do? Trying promox restore first and then if its still not working a new instance?
If the DB is external then it will not work I'm afraid
yeah
Also don't store your DB on an external drive π
and yes
you are also right π
Auto dumps are gone? I didnβt read back
auto dumps?
where to find them?
that's the UPLOAD_LOCATION/backups folder that wasn't there
Should be here but alas
one moment

yeah nothing there
ok i mean tbh
i dont have any other chance
i need to setup a new instance
i think my wife will kill me
Everything important is backed up, that's what matters π
yeah you are right
would it be ok fpor you to guide me through the process? really frightened to mess it up
you'll need about the same amount of storage space free as you are using now, do you have that?
uhh
I got an additional same 4TB HDD downstairs
so yeah possible
but is it ok for you when I drop you tmrw a message? Its getting a little bit late and I can prepeare the HDD tmrw
It's late for me too π
but I'll quickly summarize
Set it up like you would a new instance, be sure to use a new location for everything, including the compose folder env file etc. It's all fresh so carrying over passwords doesn't matter right. π
Set DB_DATA_LOCATION on a local disk (SSD preferred)
Set UPLOAD_LOCATION to your new storage location of course
Set up Immich like you would new
Does your wife have a seperate account?
in either case, you can use immich-cli or immich-go to mass upload, if there are seperate accounts you'll want to check the old UPLOAD_LOCATION/library if you were using storage templating for the user folders
If you were not using storage templating the files are inside UPLOAD_LOCATION/upload
let me just check something
These folders have a subfolder per user
because I did updatet the mini PC with an internalt SATA drive
then i set up and rsync for backup up my pictures on the external one
and cloned the drive before
i am confused
need to check proxmox and OMV
maybe i have already cloned / backup the HDD
maybe there is some hope
when i updated the mini pc with the internal sata i cloned the whole external drive to my internal one
what I missed was updating the env file
therefor on my internal new sata i must find the old DB
would it help?



so maybe using the "old" DB on my SATA?
worth a try
but to be honest
I am not sure if i am working on the right container
because if everything was cloned, there must be an identical container on SATA

need to take a rest. will check it tmrw
than you very very much for your help so far!
doesnt make any change π¦
Changed env to
DB_DATA_LOCATION=/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/docker_data
but still the same. Postgress restarting 24 7
will copy over the content to the internal hdd this weekend
How much space do you have left on your current?

sdb1 = new SATA / internal --> 2 TB free
sdc1 = external USB SATA --> 1,9 TB free
actual upload location and DB is on sdc1
like to move everything to sdb1
what do you have in mind?
sda1 is by the way the SSD where proxmox is installed. So I can also go for this one for the DB
I was thinking if you have the space free to just upload to the same disk, but it's probably a spinning disk right?
so copying to a different disk might actually be faster here :p
yeah u r right
will copy over the files the next days
I only need to copy the "upload location" right?
DB is not needed any more
well no
upload location includes thumbs and transcodes etc
you'll want the "library" or "upload" folder within UPLOAD_LOCATION
(I know the names are confusing/double)
ok thanks
wikk use cp -a to copy everything over to the SATA
I mean cp -ar
already copying, but i need to copy the content from another folder and merge them
when its done I will drop here a message

ok here we are
I have "libary" and "upload".

How to identify which should be kept and which can be deleted?

two accounts are used: wife, me
Just get a size on disk of both folders then you'll know
like
du -xhcd1 /bla/bla/upload
and du -xhcd1 /bla/bla/library
root@openmediavault:/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder# du -sh library/
342G library/
root@openmediavault:/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder# du -sh upload/
9,7G upload/
libary: 342GB
upload: 9,7GB
I mean yes, must be libary but a little bit disturbing that upload is 9,7GB "big"
Those are failed uploads and the newer versions automatically removed them, but it doesn't go back in the past
uploaded is filled with this'

yeah that's normal
+ok
so I delete everything expect libary
Yep
ok done
so now i need to setup docker correctly in/on OMV
are you by the way familiar with docker/portainer on OMV?
realy want to avoid any mistakes
I mean I already set it up
just want to be sure if everything is correctly configured
and using portainer is not a "must have" for me
not "on OMV" no :p
working on it
is it possible that I am running two instances of docker? is it technical possible? Just want to be sure dont mess it up again
ok got it running π
so can you help me how to proceed?
admin account (myself) is added
so now I add in this account the folder/pictures of my copied pictures?
but only the folder "admin" from libary I guess!?
you wrote I can use immich-go. So now I need to go to my old libary/admin copy immich-go and run it!?
sorry not the great in this stuff
Yep yep, you get immich-go, make it upload the old folder to the new immich
https://github.com/simulot/immich-go
Note they have a "dry run" option just to show you what would happen
ok
downloaded the version
I need now to copy it to the old libary/admin right on my NAS right?
need to make this step by step
what do you mean copy it
it's a program, you run it wherever and just refer it to the right directories
ah ok
puh
ok so immich-go is in my local (macos) download folder)
I must navigate now to my local immich-folder!?
here are my pictures of "admin": /srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder/library/admin
how do I write now the command that immich-go which is localy installed copy over the pictures from the location
/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder/library/admin
?
already prepared the command
immich-go -server=http://10.5.0.5:2283 -key=SECRET upload -dry-run -create-albums --album="ALBUM NAME"
by the way I am now localy in the folder of immich-go with CLI
you literally add
/srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder/library/admin
to the end of the command
don't forget to switch api key for your wifehahaha
thx
yeah will do but first i try to add my picture
just before messing anything up
hm
"zsh: command not found: immich-go"
do you know what I am doing wrong?
got it. must start with ./immich-go...
I got this error message
stat /srv/dev-disk-by-uuid-22f7f90f-63e2-4aae-9125-ba7f790e50de/Bilder/library/admin: no such file or directory
do I need to add anything like ssh or something like this?
because the path is not locally. It's on my NAS
like ssh user@IP-Address and then the path!?
ah you're trying to do it over the network
yes
uhhh probably best to mount it locally I guess
ok on it
would be better to run immich-go on the remote system
ok also for me
but how to topyit over?
and where should I put it
ok got it on my NAS i thnik
unable to run
i think I now read another version not Mac OS
yeo its running now

I think it will take some time
can I shutdown my laptop? its running on the server therefore yes!?
uhhhh
No
It's running on the server in a terminal you have openend through ssh
ok
let it run
if you close your laptop it will kill the ssh session
right makes sense
(this is what tmux/screen is for)
(you can try
ctrl+z
if your shell supports that)ok so I will upload all my stuff, then create my wifes account and then copy her stuff from old libary/sdkfjsfsdlkj (cryptic name)
and then I am done with setting everything up again I guess
Want to say thanks for the great support here. Actual I am recovering the pics from my wife and everything is working right now. Thanks for you time, thanks for the volunteer work on this great project especially @Mraedis . Its just stunning how much time and effort you spend β€οΈ THANKS!
No problem π Always happy to help (well at least most people)
just awesome thank you very much! Pics are very crucial especially with two kids βΊοΈ
Hey again
I have just a short question
I transfered with immich-go all pics successfully. Took some time but yeah it worked
Immich was under "task" running a lot of tasks, also still today (video transcoding)
I think round about 5k left
Then I saw a new version is live. so compose down, pull up
everything is working fine
BUT all task were "done" nothing left
Did I made the mistake to update without letting immich complete the whole tanscoding part!?
Well yes, no
just click the 'missing' button for transcodes
ah
great π
its running
thought i messed it up again haha
thanks again π
have a great friday and weekend!