mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3708] Proxy-Host creation via cli or api #2446
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#2446
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 @LukasBastianGTM on GitHub (Apr 19, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3708
Hey together,
I would like to add proxy hosts cia api or cli. Background is a automation in a software our company is building. We already have a large number of instances running with many proxy hosts so completely switching would nether be wanted nor practical.
We provide webservers for a application that need to be exposed. What better than a rverse proxy for that. At the moment there ist and was just a small amount of newly installed and konfigured servers in the background but we are working on scaling the finished product. I have not found a elegant way to implement new proxy hosts in a way that can be automated with a reasonable time investment for us.
ATM we would need to create a Konfiguration file, an access file, an error file, alter the db and reload nginx to get a new host.
I think many would apreciate a way of doing this easier. My first thoughts went towards an official http api or a command that can be built by other scripts our software and then executed on the proxy server.
Is this in the scope of the project or is that something that can/will not be done for whatever reasons there may be (idk how to wirte this nicely. I am not a native english speaker. This is ment in the best way possible. I am certain you have very valid reasons, if you can not/dont want to do this).
@github-actions[bot] commented on GitHub (Oct 25, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Oct 29, 2025):
Issue was closed due to inactivity.