Skip to content

NPM to pass through to another container that has it's own LE Certs. #461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Shifter2600 opened this issue Jun 16, 2020 · 2 comments
Closed

NPM to pass through to another container that has it's own LE Certs. #461

Shifter2600 opened this issue Jun 16, 2020 · 2 comments
Labels
product-support stale

Comments

@Shifter2600
Copy link

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?
@ctops1 ctops1 mentioned this issue Jan 31, 2021
Open
@github-actions GitHub Actions
Copy link

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

@github-actions github-actions bot added the stale label Mar 28, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented May 8, 2025

Issue was closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
product-support stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Shifter2600