[GH-ISSUE #461] NPM to pass through to another container that has it's own LE Certs. #388

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

Originally created by @Shifter2600 on GitHub (Jun 16, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/461

I have Nginx Proxy Manager as my 1st point of entry into my network for 80,443 which then routes out to the various containers. However I have a GitLab container that I wish to have using it's own built in LetsEncrypt setup for certs. I am trying to reverse proxy through the git.domain.com to that container just as HTTP to the IP and Port and wanting to get the GitLab Container pulling it's own certs using it's own lets encrypt. Is this possible? And If so is there anything special needed for the 1st point of entry Nginx Reverse Proxy?

Originally created by @Shifter2600 on GitHub (Jun 16, 2020). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/461 I have Nginx Proxy Manager as my 1st point of entry into my network for 80,443 which then routes out to the various containers. However I have a GitLab container that I wish to have using it's own built in LetsEncrypt setup for certs. I am trying to reverse proxy through the git.domain.com to that container just as HTTP to the IP and Port and wanting to get the GitLab Container pulling it's own certs using it's own lets encrypt. Is this possible? And If so is there anything special needed for the 1st point of entry Nginx Reverse Proxy?
kerem 2026-02-26 06:32:39 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 28, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:2024254551 --> @github-actions[bot] commented on GitHub (Mar 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2861264329 --> @github-actions[bot] commented on GitHub (May 8, 2025): Issue was closed due to inactivity.
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#388
No description provided.