vault backup: 2024-05-19 09:52:53
This commit is contained in:
parent
cd7cab0fbd
commit
c2ca2d7912
@ -3,10 +3,9 @@ This file documents my troubleshooting methodology for configuring nginx to reve
|
||||
## Context
|
||||
I have an OpenVPN server set up on a Raspberry Pi (`192.168.0.2`) listening on TCP/443 so that it's able to function on most networks. There are enough clients configured that I do not want to remake the server, then update config files for all the clients, and so on.
|
||||
|
||||
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 service and
|
||||
|
||||
I would like to serve https traffic from a server (`192.168.0.6`)
|
||||
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
|
||||
|
||||
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