[GH-ISSUE #1247] ERR_CONNECTION_REFUSED when using proxmox as proxy host #1013

Closed
opened 2026-02-26 06:35:25 +03:00 by kerem · 3 comments
Owner

Originally created by @dasbootbee on GitHub (Jul 18, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1247

Proxmox is configured to use it's default self-signed SSL certificates.

Here is the config on NPM:

{
"id": 7,
"created_on": "2021-07-18T01:57:08.000Z",
"modified_on": "2021-07-18T02:11:33.000Z",
"owner_user_id": 1,
"domain_names": [
"proxmox.mydomain.net"
],
"forward_host": "192.168.1.103",
"forward_port": 8006,
"access_list_id": 1,
"certificate_id": 1,
"ssl_forced": true,
"caching_enabled": false,
"block_exploits": false,
"advanced_config": "",
"meta": {
"letsencrypt_agree": false,
"dns_challenge": false
},
"allow_websocket_upgrade": true,
"http2_support": false,
"forward_scheme": "https",
"enabled": 1,
"locations": [],
"hsts_enabled": false,
"hsts_subdomains": false
}

Connecting directly to the IP/port via https works (get a cert warning as expected with self-signed cert on Proxmox). When I connect via the NPM configured URL I get the ERR_CONNECTION_REFUSED. Do I need some custom config to get this working? Does NPM support self-signed certificates on the proxy host?

Thank you

Originally created by @dasbootbee on GitHub (Jul 18, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1247 Proxmox is configured to use it's default self-signed SSL certificates. Here is the config on NPM: { "id": 7, "created_on": "2021-07-18T01:57:08.000Z", "modified_on": "2021-07-18T02:11:33.000Z", "owner_user_id": 1, "domain_names": [ "proxmox.mydomain.net" ], "forward_host": "192.168.1.103", "forward_port": 8006, "access_list_id": 1, "certificate_id": 1, "ssl_forced": true, "caching_enabled": false, "block_exploits": false, "advanced_config": "", "meta": { "letsencrypt_agree": false, "dns_challenge": false }, "allow_websocket_upgrade": true, "http2_support": false, "forward_scheme": "https", "enabled": 1, "locations": [], "hsts_enabled": false, "hsts_subdomains": false } Connecting directly to the IP/port via https works (get a cert warning as expected with self-signed cert on Proxmox). When I connect via the NPM configured URL I get the ERR_CONNECTION_REFUSED. Do I need some custom config to get this working? Does NPM support self-signed certificates on the proxy host? Thank you
kerem closed this issue 2026-02-26 06:35:25 +03:00
Author
Owner

@zeroone82 commented on GitHub (Jul 21, 2021):

You should share your error and access logs.

<!-- gh-comment-id:884404230 --> @zeroone82 commented on GitHub (Jul 21, 2021): You should share your error and access logs.
Author
Owner

@dasbootbee commented on GitHub (Jul 21, 2021):

I did something dumb. I had DNS pointing to my Proxmox host not NPM.

<!-- gh-comment-id:884420638 --> @dasbootbee commented on GitHub (Jul 21, 2021): I did something dumb. I had DNS pointing to my Proxmox host not NPM.
Author
Owner

@dancarvajc commented on GitHub (Feb 5, 2025):

I did something dumb. I had DNS pointing to my Proxmox host not NPM.

You saved my day! I had this same problem and now it's working...thanks!!

<!-- gh-comment-id:2635680875 --> @dancarvajc commented on GitHub (Feb 5, 2025): > I did something dumb. I had DNS pointing to my Proxmox host not NPM. You saved my day! I had this same problem and now it's working...thanks!!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1013
No description provided.