Page 1 of 1

Error 502 Bad Gateway on All Domains

Posted: Tue Jun 13, 2017 1:41 am
by BlurgeTurge
I recently configured VestaCP on a Debian instance, but I am struggling to configure my domains and DNS, as all my domains resolve to "Error 502 Bad Gateway".

I have:
  • Pointed my domains to my public IP
  • Opened port 80 on my vestaCP instance
  • Set the firewall to accept and allow outgoing connections through port 80 and port 443
  • Added a new domain for my domain
However, when connected with CloudFlare, the request times out and receives no response.
  • How can I test that a URL works? POSTMan will not allow me to send custom requests with the header "Host" set to my domain to verify
  • Is it required to set the corresponding "DNS Site"'s template to "CHILD-NS" in order to use cloudflare?
  • How can I troubleshoot my 502 bad gateway errors?