vault backup: 2024-05-19 09:53:53
This commit is contained in:
parent
c2ca2d7912
commit
149210e424
@ -5,7 +5,9 @@ I have an OpenVPN server set up on a Raspberry Pi (`192.168.0.2`) listening on T
|
|||||||
|
|
||||||
I have a Debian VM running on `192.168.0.6` that runs an "nginx hub" that I'd like to proxy all web-ish traffic out of my network with. It's currently handling at least one http(s) service running from that same VM, and will probably handle more.
|
I have a Debian VM running on `192.168.0.6` that runs an "nginx hub" that I'd like to proxy all web-ish traffic out of my network with. It's currently handling at least one http(s) service running from that same VM, and will probably handle more.
|
||||||
|
|
||||||
Given I only have one external IP, I want the ability to handle both OpenVPN traffic and https traffic
|
Given I only have one external IP, I want the ability to handle both OpenVPN traffic and https traffic on port TCP/443. I know it's possible to reverse proxy raw t
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
Right now, it appears that I can't do that with one IP because that would require two separate nginx components listening on the same port, or that's what I ascertained from the logs.
|
Right now, it appears that I can't do that with one IP because that would require two separate nginx components listening on the same port, or that's what I ascertained from the logs.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user