mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1439] Either add <ip>:port support to proxy hosts or add https support to port streams #1116
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#1116
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 @gomme600 on GitHub (Sep 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1439
Hi there,
I am looking to add https to a local server. I have generated a custom ssl certificate and I have added it. The problem is that nginx proxy manager wants a hostname (I can't create one for the purpose of this project) whereas I want to use an IP adresse. I want to be able to go <server_ip>:port and be "proxied" to a HTTP server (LAVA) but via HTTPS.
Is this possible?
Thanks
@chaptergy commented on GitHub (Sep 28, 2021):
It might be possible, but it would require for your npm instance host to be assigned multiple IP addresses, so your proxy knows from the IP address to which other machine it would have to forward it. So each proxied service would need its own IP address, and a different one for the proxy instance.
Adding an IP address as a domain name is generally possible in NPM.
@gomme600 commented on GitHub (Sep 28, 2021):
Thanks for the tip. I already have 2 IPs on this machine. The LAVA server is running on the same machine as npm aswell. So I would need 3 IPs then ? Currently both IPs point to npm and inputting them into the domain name field doesn't work, I just get the npm "It work's!" page.
@gomme600 commented on GitHub (Sep 28, 2021):
Ok so it works! In fact, after rebooting I was able to redirect xx.xx.xx.17 to xx.xx.xx.17:81 with the proxy host so I don't know if I actually need multiple IPs afterall!