We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Error 502 Bad Gateway on All Domains
-
- Posts: 1
- Joined: Tue Jun 13, 2017 1:00 am
Error 502 Bad Gateway on All Domains
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:
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
- 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?