• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Issue with cloudflare and Plesk, Error 522

Korkodilos_

New Pleskian
Having an issue today. Not sure if it's Plesk or Cloudflare related. All my website with DNS managed in cloudflare, are getting an error 522 from cloudflare.

I checked banned IPs, didn't find any cloudflare IPs, but whitelisted them all anyway. Also turned off the WAF, still the same.

I know that chances are that it's a cloudflare issue, any ideas if there's something i could do to solve it? No changes have been made to the server.
 
hello @Korkodilos_ ,

when you're doing nslookup of your domains - what IP displayed for them?
real IP of your server or cloudflare ?

if you add IP of you server for some of your domain to the hosts and try to open it - will it work or it will continue return error 522 ?

actually, error 522 mean that cloudflare is not able connect to your servers by some reasons. So you need to identify, is your server works or this is a problem with communication between your Plesk and Cloudflare.
 
When I visit with VPN from different location, websites work. When visiting from my IP (Greece) i'm getting error 522.

Some development sub domains that I have without proxy, work fine from all locations. My guess is that it's a Cloudflare issue with Greek Internet Providers or something. i'll give it some time....
 
Back
Top