

0·
23 hours agoIf it’s 192.168.1.1, then your DNS has the wrong address somewhere. It’s looking for 35.242
If it’s 192.168.1.1, then your DNS has the wrong address somewhere. It’s looking for 35.242
You have a loopback. Says it right there.
From your diagram it looks like you’re have two reverse proxies chained together…why?
Read your own screenshot
If you want to simplify things, do this:
Then just keep adding things back and find where it’s breaking. I’m positive you have a hostname mismatch, or a messed up DNS record if you’re using multiple proxies. Curl output would be helpful. Also check
dig (hostname)
to see what your DNS is responding with.