SSL Error 522 after IP change

I decided to move the site to my secondary server, first moving the test subdomain. The SSL version of the moved subdomain seems to be stuck in 522.

There is another preexisitng site on the second server using the very same key, and all keys, directories, and permissions are identical.

Did you go through this:

There is a preexisting other domain which works fine with SSL, using the same keys which proves SSL is in deed working and 443 is open. It also proves that it is a known working key.

In addition, the standard http version for the moved site is working which proves that the configuration is sound in terms of apache, and it is connecting with port 80 for the moved site

The second server is also using an identical security profile as the first, literally the same one in my hosting provider, meaning that all port setting are identical across the first and second server.

Both operating systems are the same, ie the servers are clones from the same parent clone.

Error 522 usually does not related to SSL cert issue.

Did you check whether port 80 and 443 are already open in your server and there’s no firewall blocking Cloudflare IPs?

I see that the moved site works for http, but not https.

The preexisting site working with SSL and standard http proves that both 80 and 443 are open for the second server.

Ok good idea about the security groups. They were not the same group. The second server did not have a rule to allow 443.

I assumed it was the same group, because the second server was processing HTTPS for a naked domain. My assumption was based upon that.

This implies that the hosting provider has a bug in their security which was allowing 443 for naked domains, when it was not specifically allowed, and when a subdomain attempted the same thing it was denied.

You are awesome sir.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.