1.5 billion windows users, another million transfers to 1.499 billion windows and +0.001 billion Linux. The windows number was purely from Google, no validation has been done.

Nobody knows everyone else’s definition of everything. Many might call the people you know tech enthusiasts or tech heads or something else. No big deal.

https://www.urbandictionary.com/define.php?term=tech+bro

If you’re hanging out with what most call a tech bro, I’m kind of impressed bit still don’t really care for what you say.

404 is a web server response suggesting that a web server is up. It’s what’s giving 404.

The web server can’t find your page or document or resource. So one of your web servers (on either the reverse proxy or the actual server) is pointing to the wrong spot on what to serve.

You haven’t tried launching a wrong server on the same port right? Or misconfigured your nginx translation?

Isolate the issue. Ignore nginx and start testing just the web server on the destination and see if the server is giving 404 and then if it is giving the right document then it’s nginx configuration. If it’s not giving you the document nginx can’t serve.

But either way start isolating the problem into the smallest area. And focus on the configurations and files that are related to it.