From 1bc828ffea9e5149a6e7f4faf6cae54eebff26ff Mon Sep 17 00:00:00 2001 From: zleyyij Date: Sun, 19 May 2024 09:47:53 -0600 Subject: [PATCH] vault backup: 2024-05-19 09:47:53 --- ...king nginx forward VPN and https traffic on tcp 443.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/IT/Making nginx forward VPN and https traffic on tcp 443.md b/IT/Making nginx forward VPN and https traffic on tcp 443.md index 05c8e58..6f94d4f 100644 --- a/IT/Making nginx forward VPN and https traffic on tcp 443.md +++ b/IT/Making nginx forward VPN and https traffic on tcp 443.md @@ -1,5 +1,9 @@ This file documents my troubleshooting methodology for configuring nginx to reverse proxy https traffic, and reverse proxy non https traffic on tcp/443. +## Context +I would like to serve https traffic from a server (`192.168.0.6`), + + 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. I modified `/etc/nginx/nginx.conf` to include this block underneath the `http` block: @@ -12,4 +16,8 @@ stream { } ``` +When trying to start with that change applied, I got the error: +``` +nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) +``` ## IP Aliasing