From 80cf75661a883d43b67ad7add54e272743fe87a0 Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 10:56:06 -0600 Subject: [PATCH] vault backup: 2024-05-19 10:56:06 --- .../Making nginx forward VPN and https traffic on tcp 443.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename IT/{ => Troubleshooting}/Making nginx forward VPN and https traffic on tcp 443.md (98%) diff --git a/IT/Making nginx forward VPN and https traffic on tcp 443.md b/IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md similarity index 98% rename from IT/Making nginx forward VPN and https traffic on tcp 443.md rename to IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md index 35a8ea3..abf88d9 100644 --- a/IT/Making nginx forward VPN and https traffic on tcp 443.md +++ b/IT/Troubleshooting/Making nginx forward VPN and https traffic on tcp 443.md @@ -56,4 +56,4 @@ The server now starts without issue. After going through that headache, I now believe that we're back to square 1, and we have 2 IPs that both need to listen externally on 443. # Outcome -I ended up spinning u \ No newline at end of file +I ended up spinning up a new openvpn server on TCP/3389 for RDP \ No newline at end of file