Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

password authentication failed for user "dbuser" #2589

Closed
ZuluPilgrim opened this issue Apr 14, 2024 · 4 comments
Closed

password authentication failed for user "dbuser" #2589

ZuluPilgrim opened this issue Apr 14, 2024 · 4 comments
Labels
question Further information is requested stale

Comments

@ZuluPilgrim
Copy link

I have change the password for dbuser in the docker-compose file but now I get,

password authentication failed for user "dbuser"

I tried searching for 'dbuser' in the file and change all related password values to the same value, but this did not help

  • DOCSPELL_SERVER_BACKEND_JDBC_PASSWORD=mypassword
  • DOCSPELL_JOEX_JDBC_PASSWORD=mypassword
  • POSTGRES_PASSWORD=mypassword
@ZuluPilgrim
Copy link
Author

Ok, I changed it back to dbpass and all worked. Is there no security issue using a published password?

@eikek
Copy link
Owner

eikek commented Apr 15, 2024

I'm not sure I understand. If you change the password in the compose file, you of course need to change it on postgres first no? For the security concern, it all depends on how you are exposing your things. And then the provided compose file is for getting started quickly. Everyone has their own ways of running things, so just adopt as you see fit.

@eikek eikek added the question Further information is requested label Apr 15, 2024
@ZuluPilgrim
Copy link
Author

I just wanted a password that was not the default so changed it everywhere i.e. POSTGRES_PASSWORD too but it would not connect. When I put it back to dbpass, it worked again. I must have missed changing it somewhere else too. I will try again later in the week.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. This only applies to 'question' issues. Always feel free to reopen or create new issues. Thank you!

@github-actions github-actions bot added the stale label May 16, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested stale
Projects
None yet
Development

No branches or pull requests

2 participants