Recently I moved my Dell Server from one location to another, with a
completely different Router. Its Main OS/VM Manager is Proxmox VE 5.3. I got
an Nginx VM that is Reverse Proxying several other VMs.
After configuring my new Router, I got several of my VMs to connect to the
Internet (setting the same Private IPs to the same MAC Addresses, and
opening the same ports for the same Private IPs). However, with my Discourse
VM, I am receiving 502 Bad Gateway - nginx/1.14.0 (Ubuntu) when trying to
access Discourse in a Browser.
I've basically hit a point where I believe the issue is with the
configuration of the Nginx VM. Recently I've tried renewed the SSL
Certificates (using Let's Encrypt) for all my sites on Nginx, hoping it
would fix the problem ... but it didn't. However, I checked the Nginx Error
Log and found a message being reported over and over again:
* 184.108.40.206 = My Old Public IP Address
* 220.127.116.11 = My New Public IP Address
It looks to me like Nginx is trying to connect this site using my Old Public
IP Address. That is definitely incorrect.
My /etc/nginx/sites-available CONF file for the Discourse Site can be found
in THIS link: https://pastebin.com/fiiyATeP
* 192.168.0.101 = Nginx VM
* 192.168.0.104 = Discourse VM
On Sun, Nov 17, 2019 at 06:40:36AM -0500, naupe wrote:
> > root@ngx:/etc/nginx/sites-available# less /var/log/nginx/error.log
> > 2019/11/17 06:01:24 [error] 23646#23646: *37 connect() failed (111:
> Connection refused) while connecting to upstream, client: 18.104.22.168, server:
> discourse.domainame.com, request: "GET / HTTP/2.0", upstream:
> "http://22.214.171.124:8080/", host: "discourse.domainame.com"
> * 126.96.36.199 = My Old Public IP Address
> * 188.8.131.52 = My New Public IP Address
nginx is trying, and failing, to connect to 184.108.40.206:8080.
Should nginx be trying to connect to 220.127.116.11? If so, fix the network so
that it is able to connect there. If not, fix the nginx config so that
it tries to connect to the place that you want.