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

docs: standalone psql pg_hba.conf error help #14570

Closed
wants to merge 1 commit into from

Conversation

WillForan
Copy link

No description provided.

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Dec 8, 2024
Copy link
Contributor

github-actions bot commented Dec 8, 2024

Label error. Requires exactly 1 of: changelog:.*. Found: documentation

@mmomjian
Copy link
Contributor

mmomjian commented Dec 8, 2024

Thanks for the PR. I really don’t know how I feel about adding such basic Postgres knowledge to our docs.

if you don’t already know how to do this, my opinion is that you should not use a standalone postgres. Perhaps others disagree with me, though.

@WillForan
Copy link
Author

WillForan commented Dec 8, 2024

Thanks for looking and I can agree. The error message is relatively straight forward and easily searched (though I can only say that now with the clarity of hindsight).

The part that caught me: I (erroneously) thought I'd already allowed all of ipv4 in my config and was convinced Immich was ignoring DB_URL for a docker-compose connection (or something). I also went for a SSL tangent thinking the the "no encryption" part implied Immich requires it.
After longer than I'd like to admit, I realize the error in the log was forwarded on from the standalone server and not related to the Immich server. ... That's probably a pretty niche confusion.

@bo0tzz
Copy link
Member

bo0tzz commented Dec 8, 2024

Thanks for the PR! I agree with mmomjian, I think this is basic postgresql admin knowledge that you should be able to figure out yourself if you choose to run a standalone database. I also think we shouldn't be telling people to set the auth to trust, because someone will blindly copy that and get their database pwned.

@bo0tzz bo0tzz closed this Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants