You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug
When enabling PostgreSQL, the dashboard throws a Bad Gateway-error and the logs print the following:
[1/14/2025] [8:47:38 PM] [Global ] › ✖ error no pg_hba.conf entry for host "xx.xx.xx.xx", user "nginx_proxy_manager", database "nginx_proxy_manager", no encryption error: no pg_hba.conf entry for host "xx.xx.xx.xx", user "nginx_proxy_manager", database "nginx_proxy_manager", no encryption
at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:283:98)
at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:122:29)
at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:35:38)
at Socket.<anonymous> (/app/node_modules/pg-protocol/dist/index.js:11:42)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
at TCP.onStreamRead (node:internal/stream_base_commons:191:23) {
length: 183,
severity: 'FATAL',
code: '28000',
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: 'auth.c',
line: '535',
routine: 'ClientAuthentication'
}
Nginx Proxy Manager Version
v2.12.2
To Reproduce
Steps to reproduce the behavior:
Go to log in screen
Login
See error.
Expected behavior
Connect to database and login to dashboard
Screenshots
PS. Stock compose file, also tried with the advanced vars in the compose file, but same issue.
Operating System
Debian 12
Additional context
My database is a managed one from Digital Ocean, I think the issue comes from the certificate.
This is how I normally connect to the database: postgresql://project_name:[email protected]:25060/project_name?connection_limit=5&pool_timeout=360&connect_timeout=360
The text was updated successfully, but these errors were encountered:
I just want to add to this issue as well as I encountered the same error with MariaDB hosted on another server myself.
It seem like the application is not accepting an already available database host? I tried specifying DB_MYSQL_HOST as IP and FQDN, but the log shows it is trying to access the database on npmhost (local machine docker is running on).
Error:
[1/15/2025] [7:51:48 AM] [Global ] › ✖ error Access denied for user 'npm'@'npmhost' (using password: YES) Error: Access denied for user 'npm'@'npmhost' (using password: YES)
Compose:
services:
app:
image: 'jc21/nginx-proxy-manager:latest'restart: unless-stoppedports:
# Port Format <host-port>:<container-port>
- '80:80'# Public HTTP Port
- '443:443'# Public HTTPS Port
- '81:81'# Administrator Web Portenvironment:
# MySQL/MariaDB Connection:DB_MYSQL_HOST: "10.1.1.21"DB_MYSQL_PORT: 3306DB_MYSQL_USER: "npm"DB_MYSQL_PASSWORD: "IHopeThisIsNotYourPassword"DB_MYSQL_NAME: "npm"# Disable IPv6# DISABLE_IPV6: 'true'volumes:
# Volume Format <source-volume>:<target-volume>
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
When enabling PostgreSQL, the dashboard throws a Bad Gateway-error and the logs print the following:
Nginx Proxy Manager Version
v2.12.2
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connect to database and login to dashboard
Screenshots
PS. Stock compose file, also tried with the advanced vars in the compose file, but same issue.
Operating System
Debian 12
Additional context
My database is a managed one from Digital Ocean, I think the issue comes from the certificate.
This is how I normally connect to the database:
postgresql://project_name:[email protected]:25060/project_name?connection_limit=5&pool_timeout=360&connect_timeout=360
The text was updated successfully, but these errors were encountered: