loeeeee
commented
2 months ago Sorry, this is a busy week for me. I will look into this at weekend.
Closed makovez closed 2 months ago
loeeeee
commented
2 months ago Sorry, this is a busy week for me. I will look into this at weekend.
loeeeee
commented
2 months ago Just in case, you changed the password inside /home/immich/runtime.env? Not the one in immich-in-lxc, right?
To be honest, I do not have many clues on this.
Can you try run /home/immich/app/start.sh immich as user immich, after stopping the system unit service? And tests out if the modification to the runtime.env works?
makovez
commented
2 months ago oh yeah i did. I mean, i set it first insideimmich-in-lxc and after running ./install it copied the same in /home/immich/runtime.env, so i just made sure the modified password was there too, and it was.
makovez
commented
2 months ago
Might be for this ? Is that ENV passed to api and microservices too ?
loeeeee
commented
2 months ago Might be for this ? Is that ENV passed to api and microservices too ?
They should all have been passed to microservices, and web(i.e. API). Otherwise, they would not start. The immich/app/start.sh contains the code to load the environment file.
Can you try renaming runtime.env in /home/immich/ to something else and check if it would start? I am now quite confused of how this could happen.
makovez
commented
2 months ago I just changed password and it seems working now, maybe i messed sth up before. Sorry about that.
loeeeee
commented
2 months ago I just changed password and it seems working now, maybe i messed sth up before. Sorry about that.
Never mind. 😃 Thanks for working together!
I'm encountering an issue where the DB_PASSWORD specified in the runtime.env file is not being used when Immich tries to connect to the PostgreSQL database. If I change the DB_PASSWORD in runtime.env, Immich still attempts to connect with the previous password, resulting in a connection failure.