[GH-ISSUE #1695] SSL for IP address #1266

Closed
opened 2026-02-26 06:36:28 +03:00 by kerem · 2 comments
Owner

Originally created by @dmkjr on GitHub (Dec 29, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1695

I've used NPM for quite some time now. I'm running into a problem on Home Assistant (externally presented through NPM) where I included a configurator docker instance as an iframe within the configuration.yaml

All is well except it's yelling at me for attempting mixed content. The below code was from the configuration.yaml file in Home Assistant. I need to make that http, https and was attempting to utilize NPM to handle the Let's Encrypt certificate. Is this possible? We do not want to create another subdomain "something.example.com" that routes to the internal address. I can do this, but trying to just add a certificate at the LAN level that isn't presented publicly.

panel_iframe: configurator: title: 'Configurator' url: 'http://10.0.10.100:3218' icon: mdi:wrench

Thanks community!

Originally created by @dmkjr on GitHub (Dec 29, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1695 I've used NPM for quite some time now. I'm running into a problem on Home Assistant (externally presented through NPM) where I included a configurator docker instance as an iframe within the configuration.yaml All is well except it's yelling at me for attempting mixed content. The below code was from the configuration.yaml file in Home Assistant. I need to make that http, https and was attempting to utilize NPM to handle the Let's Encrypt certificate. Is this possible? We do not want to create another subdomain "something.example.com" that routes to the internal address. I can do this, but trying to just add a certificate at the LAN level that isn't presented publicly. `panel_iframe: configurator: title: 'Configurator' url: 'http://10.0.10.100:3218' icon: mdi:wrench` Thanks community!
kerem 2026-02-26 06:36:28 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@chaptergy commented on GitHub (Dec 29, 2021):

Letsencrypt does not provide certificates for IP addresses, just for domains. It is generally unusual to have a certificate for an IP, except when it is a self signed certificate. And then no browser would trust this certificate, meaning you would either have to click "accept the risk" in every browser or install the certificate on every device you use.

Furthermore to route without a domain in nginx, the proxy would have to be set as the default server. Meaning everything received by nginx where it does not know where to route it to will be routed there. In npm this default server is already taken by the default page / congratulations page, so you can't do that in npm.

So what you are asking is not possible. SSL would either have to be handled by the proxied app and you can create a stream host for it, or you need a domain which you use to redirect to there.

<!-- gh-comment-id:1002479189 --> @chaptergy commented on GitHub (Dec 29, 2021): Letsencrypt does not provide certificates for IP addresses, just for domains. It is generally unusual to have a certificate for an IP, except when it is a self signed certificate. And then no browser would trust this certificate, meaning you would either have to click "accept the risk" in every browser or install the certificate on every device you use. Furthermore to route without a domain in nginx, the proxy would have to be set as the default server. Meaning everything received by nginx where it does not know where to route it to will be routed there. In npm this default server is already taken by the default page / congratulations page, so you can't do that in npm. So what you are asking is not possible. SSL would either have to be handled by the proxied app and you can create a stream host for it, or you need a domain which you use to redirect to there.
Author
Owner

@dmkjr commented on GitHub (Dec 29, 2021):

@chaptergy Thank you for the response. I can certainly do the reverse proxy by domain name. Perhaps I can find ways to lock it down outside of my normal Cloudflare policies. Thank you for the information.

<!-- gh-comment-id:1002610148 --> @dmkjr commented on GitHub (Dec 29, 2021): @chaptergy Thank you for the response. I can certainly do the reverse proxy by domain name. Perhaps I can find ways to lock it down outside of my normal Cloudflare policies. Thank you for the information.
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#1266
No description provided.