#password authentication failed for user "postgres"

1 messages · Page 1 of 1 (latest)

untold smelt
#

after trying to update server in dockage postgres keeps saying password auth failed, i have not changed the password in the .env, i also tried to make a .env file with the same information in dockage in the same folders but the issue still persists

long pikeBOT
#

:wave: Hey @untold smelt,

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

#

Checklist

I have...

  1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: reviewed Github for known issues.
  5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :ballot_box_with_check: uploaded the relevant information (see below).
  7. :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 -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.

long pikeBOT
untold smelt
#

i have made sure to use the current docker compose and .env files, and just adjusted db password

frail oyster
#

You're making contradictory statements 😅

untold smelt
#

i changed the db pw in the .env after re copying it to the same password i already had

frail oyster
#

I don't follow

#

Why/when has the password changed in the .env file?

#

Why did you have to paste it there again?

untold smelt
#

i just re copied the cocmpose and env file from the github to make sure it was correct

#

then changed the pw in the newly copied env to the pw i set

frail oyster
#

There's no need to do that

#

From which version did you upgrade?

#

How did your old compose and env file look like?

untold smelt
#

130.2

#

it should have been the defult, i didnt change anything

frail oyster
#

What are you using exactly? Which OS? etc.

#

I'm not aware of "dockage"

untold smelt
#

proxmox lxc using dockage

frail oyster
#

I have no clue what dockage is

#

But docker in lxc is unsupported

untold smelt
#

its similar to portainer

#

but much simpler

frail oyster
#

Do you mean dockge?

untold smelt
#

yes my bad

frail oyster
#

Gotcha

frail oyster
untold smelt
#

is that an issue with proxmox? or just immich?

frail oyster
#

Proxmox officially says that you shouldn't be running docker inside LXC

untold smelt
#

okay i was not aware of that, but this doesn't seem to be a docker issue to me, its just not getting the correct pw?

solar kiln
frail oyster
#

Oh actually

#

How did you start the stack again after changing your .env file?

untold smelt
frail oyster
frail oyster
untold smelt
#

yeah everything looks good

frail oyster
#

Are you sure it was using your password before then?

untold smelt
#

im not 100% certin, but i changed the pw to what i set it to and then it worked

frail oyster
#

Yeah, so it must've not been that password in the past :P

untold smelt
#

i will look into migrating to a VM ofr the future

frail oyster
#

Anyways. We still recommend moving to a VM, since we have in fact seen weird (in parts irrecoverable) issues with running docker in proxmox LXC in the past

frail oyster
untold smelt
#

im guessing dockge doesn't pass through the .env that well? that's my best guess

#

or i did something wrong, much more likely....

frail oyster
#

¯_(ツ)_/¯

untold smelt
#

thanks for the assistance!