starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

PostgreSQL LXC - can't authenticate via Adminer #72

New Issue
Closed
opened 2026-02-04 16:27:30 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 16:27:30 +03:00
Owner
Copy Link

Originally created by @chris400 on GitHub (Nov 18, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

The default configuration requires to create a linux user along with the postgresql. To avoid this I had to update the pg_hba.conf changing the following line
local all all peer
to
local all all md5

See https://gist.github.com/AtulKsol/4470d377b448e56468baef85af7fd614

My suggestion would be to either update the deployment script or put a note on the script.

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Deploy the container and try to access the db server via Adminer

Originally created by @chris400 on GitHub (Nov 18, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. The default configuration requires to create a linux user along with the postgresql. To avoid this I had to update the pg_hba.conf changing the following line `local all all peer` to `local all all md5` See https://gist.github.com/AtulKsol/4470d377b448e56468baef85af7fd614 My suggestion would be to either update the deployment script or put a note on the script. ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. Deploy the container and try to access the db server via Adminer
OVERLORD added the maintenance label 2026-02-04 16:27:30 +03:00
OVERLORD commented 2026-02-04 16:27:43 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Dec 2, 2024):

I could reproduce the error i think, i´working on a fix.

@michelroegl-brunner commented on GitHub (Dec 2, 2024): I could reproduce the error i think, i´working on a fix.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label maintenance
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#72
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?