starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #110] Proxying to container with self signed https access #99

New issue

Closed

opened 2026-02-26 05:34:30 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 05:34:30 +03:00

Owner

Originally created by @tiagombrito on GitHub (Mar 25, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/110

Hello,

I'm trying to create a docker-compose stack in portainer, with nginx-proxy-manager and keycloak, among other apps.

When accessing keycloak via https://hostname:8443 I'm able to access the application, since the container has a self signed cert in it.

Yet i'm not able to do it via npm, I create a proxy host with domain "keycloak.domain", https scheme, pointing to container:8443, and when accessing https://keycloak.domain i get an error (This site can’t provide a secure connection), yet i'm still able to access it via http.

The configuration file shows nginx is listening on port 80 instead of 443, probably because i didn't use letsencrypt (I'm just experimenting with https, and don't want the domain visible outside the local network), nor did i give npm the cert files, since i was expecting to use the ones in the keycloak container.

Is this not possible, or am i doing it wrong?

EDIT: Creating a custom certificate and adding it to npm and the proxy host seems to work just fine.

Thank you, and i hope that was coherent.

Originally created by @tiagombrito on GitHub (Mar 25, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/110 Hello, I'm trying to create a docker-compose stack in portainer, with nginx-proxy-manager and keycloak, among other apps. When accessing keycloak via https://hostname:8443 I'm able to access the application, since the container has a self signed cert in it. Yet i'm not able to do it via npm, I create a proxy host with domain "keycloak.domain", https scheme, pointing to container:8443, and when accessing https://keycloak.domain i get an error (This site can’t provide a secure connection), yet i'm still able to access it via http. The configuration file shows nginx is listening on port 80 instead of 443, probably because i didn't use letsencrypt (I'm just experimenting with https, and don't want the domain visible outside the local network), nor did i give npm the cert files, since i was expecting to use the ones in the keycloak container. Is this not possible, or am i doing it wrong? EDIT: Creating a custom certificate and adding it to npm and the proxy host seems to work just fine. Thank you, and i hope that was coherent.

kerem closed this issue

2026-02-26 05:34:30 +03:00

kerem commented

2026-02-26 05:34:31 +03:00

Author

Owner

@jc21 commented on GitHub (Mar 27, 2019):

What you're experiencing is expected behaviour. The edge server (NPM) is not configured for SSL termination so you have to use http - no matter what the upstream server uses. It's functioning as a proxy, just not a secure one until you create or add certificates.

@jc21 commented on GitHub (Mar 27, 2019): What you're experiencing is expected behaviour. The edge server (NPM) is not configured for SSL termination so you have to use `http` - no matter what the upstream server uses. It's functioning as a proxy, just not a secure one until you create or add certificates.

kerem commented

2026-02-26 05:34:32 +03:00

Author

Owner

@tiagombrito commented on GitHub (Mar 27, 2019):

Thank you.

Since I have my solution, I'll close the issue.

@tiagombrito commented on GitHub (Mar 27, 2019): Thank you. Since I have my solution, I'll close the issue.

kerem commented

2026-02-26 05:34:32 +03:00

Author

Owner

@goodvandro commented on GitHub (Apr 7, 2023):

@tiagombrito How did you solve your problem? Can you share the steps with me?

@goodvandro commented on GitHub (Apr 7, 2023): @tiagombrito How did you solve your problem? Can you share the steps with me?

kerem referenced this issue

2026-02-26 07:38:23 +03:00

[PR #99] [MERGED] This commit resolves #98 so custom location can forward to custom path. #3188

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

No description provided.

Rows
Columns