mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #3413] Its not BUG , Its Question #2283
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2283
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Askeshine on GitHub (Dec 23, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3413
Hlelo sorry for make this issue but i have question.
I running nginx web server with 30 websites, i can install nginx proxy manager too ?
i want UI for proxy manager but i dont want lost websites (? i explain?
@ignas2526 commented on GitHub (Jan 1, 2024):
Hi,
Depends on your setup and what's your goal. If you're using docker, just run an official Nginx Proxy Manager (NPM) image alongside your existing stuff. If you have virtual machines or virtual servers, e.g. GCP or AWS, then you'd want to spin up a separate server for NPM.
You can then migrate a couple of websites to NPM and see how it goes. Nginx servers can proxy traffic from one to another, so you can have NPM send traffic to the existing Nginx server initially.
@github-actions[bot] commented on GitHub (Jul 15, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Aug 6, 2025):
Issue was closed due to inactivity.