starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #3992] Not sure if this is NPM issue or not.... #2608

New issue

Closed

opened 2026-02-26 07:36:12 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:36:12 +03:00

Owner

Originally created by @ccheath on GitHub (Sep 12, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3992

I setup NPM following this video "Quick and Easy Local SSL Certificates for Your Homelab!"
Only difference is that I have my own domain (not duckdns) and have it's DNS controlled by Cloudflare.
(which he shows very briefly as an alternative to duckdns)

Everything went smooth, but at the end all my services loaded in http not https.
I double-checked everything that I could think of and everything was set correctly.
Then I began to get "site can't be reached" ERR_CONNECTION_REFUSED browser messages.

I've removed all the proxies and tried to create them again but no matter what I do they all give that same ERR_CONNECTION_REFUSED message.

I can't see any errors in the docker container logs for NPM, and I'm a bit lost here... can anyone suggest some things to troubleshoot?

TYIA

Originally created by @ccheath on GitHub (Sep 12, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3992 I setup NPM following [this video](https://www.youtube.com/watch?v=qlcVx-k-02E) "Quick and Easy Local SSL Certificates for Your Homelab!" Only difference is that I have my own domain (not duckdns) and have it's DNS controlled by Cloudflare. (which he shows very briefly as an alternative to duckdns) Everything went smooth, but at the end all my services loaded in http not https. I double-checked everything that I could think of and everything was set correctly. Then I began to get "site can't be reached" ERR_CONNECTION_REFUSED browser messages. I've removed all the proxies and tried to create them again but no matter what I do they all give that same ERR_CONNECTION_REFUSED message. I can't see any errors in the docker container logs for NPM, and I'm a bit lost here... can anyone suggest some things to troubleshoot? TYIA

kerem closed this issue

2026-02-26 07:36:12 +03:00

kerem commented

2026-02-26 07:36:13 +03:00

Author

Owner

@ccheath commented on GitHub (Sep 13, 2024):

update: after sleeping on this and checking again today my services are again reachable, but again are also not secured http (not https)...

how can i troubleshoot this?

@ccheath commented on GitHub (Sep 13, 2024): update: after sleeping on this and checking again today my services are again reachable, but again are also not secured http (not https)... how can i troubleshoot this?

kerem commented

2026-02-26 07:36:13 +03:00

Author

Owner

@ccheath commented on GitHub (Sep 13, 2024):

well.... and again it's gone back to "site can't be reached" ERR_CONNECTION_REFUSED
this time I've done nothing to the NPM config (haven't touched it since yesterday)
just browsed to three a few login pages then went to eat dinner and after coming back to check nothing's loading

@ccheath commented on GitHub (Sep 13, 2024): well.... and again it's gone back to "site can't be reached" ERR_CONNECTION_REFUSED this time I've done nothing to the NPM config (haven't touched it since yesterday) just browsed to three a few login pages then went to eat dinner and after coming back to check nothing's loading

kerem commented

2026-02-26 07:36:13 +03:00

Author

Owner

@cjboyle commented on GitHub (Sep 16, 2024):

@ccheath We may need more info on the applications you have set up, browser messages aren't terribly helpful...

On that video around 3:18, he set scheme=https and port=80, which is incorrect and may cause issues as :80 is reserved for HTTP, not HTTPS.

It obviously depends on which ports your apps are exposing (and which protocol each is using), but make sure the scheme field is correct. For example, for Jellyfin's default ports, you might use one of (but not both):

scheme=http, port=8096 (this is what I proxy in NPM)
scheme=https, port=8920 (I don't proxy this as it requires a separate app-local certificate)

@cjboyle commented on GitHub (Sep 16, 2024): @ccheath We may need more info on the applications you have set up, browser messages aren't terribly helpful... On that video around 3:18, he set **scheme=https** and **port=80**, which is incorrect and may cause issues as :80 is reserved for HTTP, not HTTPS. It obviously depends on which ports your apps are exposing (and which protocol each is using), but make sure the scheme field is correct. For example, for Jellyfin's default ports, you might use **one** of (but not both): * scheme=http, port=8096 (this is what I proxy in NPM) * scheme=https, port=8920 (I don't proxy this as it requires a separate app-local certificate)

kerem commented

2026-02-26 07:36:13 +03:00

Author

Owner

@ccheath commented on GitHub (Sep 16, 2024):

@cjboyle thanks for the reply... I was able to get it to work yesterday by putting the IP (local/internal) address in NPM instead of the container name like he did in the video.

I also left NPM only accessible on the lan and only exposed my other services via NPM.

again, thanks

@ccheath commented on GitHub (Sep 16, 2024): @cjboyle thanks for the reply... I was able to get it to work yesterday by putting the IP (local/internal) address in NPM instead of the container name like he did in the video. I also left NPM only accessible on the lan and only exposed my other services via NPM. again, thanks

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#2608

No description provided.

Rows
Columns