Quote:
Originally Posted by kovidgoyal
The content server log wont help you in that case, as the requests are never reaching the content server. If I were you I'd double check my port forwarding rules and my firewall rules.
|
I did double check my port forwarding and firewall settings. That's why I'm a bit confused.
They match up.
I'm getting a message that says, "502 Bad Gateway Response Error, a bad response was received from another proxy server or destination origin server."
EDIT: I think I found a solution. My settings did match up with no-ip.com and I decided to try and enter the IP address and this time I added the : and my port number and that seemed to work. I don't know why in the past it wasn't needed but it appears now I have to add the port the address is going to at the end of the url. Thank you for your help. Knowing that the problem was on my end helped narrow down what could be wrong.