- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
It will take a lot more information to solve the issue you're running into fully, and I am not sure this site is the proper forum for that.
However, I do have one place you can start. HTTP 522 status codes, according to Wikipedia, indicate that Cloudflare timed out while trying to access your origin server. Be sure your DNS is configured correctly and your security settings are appropriately set. The security settings on Cloudflare can cause significant issues with communication between Cloudflare and the origin if misconfigured.
Agree with Jason - we would need a lot more information to troubleshoot. A couple of things. First, can you reach the website directly without CloudFlare in the loop? Go stright to the public address and fake out DNS by updating your computer's host file if necessary. Another thing does come to mind. On an EC2 instance, if you let a public IP be assigned at the time of creation versus manually assigning an elastic IP after creation - the public IP will be released and reassigned on reboots. This could also be your problem. Please verify your public facing IP address and then if CloudFlare is pointing to the correct one. Provide more infor and we will try to help.
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten