[GH-ISSUE #1923] Use nginx and letsencrypt that is on the server #1403

Closed
opened 2026-02-26 07:30:51 +03:00 by kerem · 5 comments
Owner

Originally created by @ririko5834 on GitHub (Mar 11, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1923

Can you add way to use nginx and letsencrypt that is on the server, not to use nginx that is created in the docker container. As if you already have nginx on ports 80 and 443 on the server, you can't use this.

I think that it's possible that you specify nginx directory (/etc/nginx) in environment where configs will be written.

Originally created by @ririko5834 on GitHub (Mar 11, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1923 Can you add way to use nginx and letsencrypt that is on the server, not to use nginx that is created in the docker container. As if you already have nginx on ports 80 and 443 on the server, you can't use this. I think that it's possible that you specify nginx directory (/etc/nginx) in environment where configs will be written.
kerem 2026-02-26 07:30:51 +03:00
Author
Owner

@caesartcs commented on GitHub (Apr 16, 2022):

So this would be possible to do. But I think the maintainer would tell you its out of scope for this project. NPM is (at least for now) created to be a dockerized container. By adding other sites to the same container, you are complicating it more than needed. The solution you would be told is to just spin a new container.

Don't get me wrong, I understand what you are trying to do and why. But I too would push for just making a new container. Its a container, not a full vm.

(Also, you are not the only one asking about this. #1919 #1913)

<!-- gh-comment-id:1100675276 --> @caesartcs commented on GitHub (Apr 16, 2022): So this would be possible to do. But I think the maintainer would tell you its out of scope for this project. NPM is (at least for now) created to be a dockerized container. By adding other sites to the same container, you are complicating it more than needed. The solution you would be told is to just spin a new container. Don't get me wrong, I understand what you are trying to do and why. But I too would push for just making a new container. Its a container, not a full vm. (Also, you are not the only one asking about this. #1919 #1913)
Author
Owner

@github-actions[bot] commented on GitHub (Feb 22, 2024):

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

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

@ririko5834 commented on GitHub (Feb 22, 2024):

It still wasnt answered by any maintainer

<!-- gh-comment-id:1959997477 --> @ririko5834 commented on GitHub (Feb 22, 2024): It still wasnt answered by any maintainer
Author
Owner

@github-actions[bot] commented on GitHub (Nov 29, 2024):

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

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

@github-actions[bot] commented on GitHub (Dec 4, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:3609691386 --> @github-actions[bot] commented on GitHub (Dec 4, 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#1403
No description provided.