Wordpress staging SSL problem

Hi there,

I have been trying to setup a staging copy of a website that is hosted on siteground. I consulted with their support and did all the necessary steps:

  1. Create staging copy (staging2.solid-run.com)
  2. Added A records to point to hosting IP
  3. Added SSL certificate via Let’s encrypt

This is the error I get now when trying to login; ERR_SSL_VERSION_OR_CIPHER_MISMATCH

When I disable cloudflare on the site, I can access the staging copy, there seems to be a problem with the SSL (set to strict on our account). Can you please help me to identify what am I missing?

Thank you,
Ilya

Check this out

https://community.cloudflare.com/t/community-tip-fixing-err-ssl-version-or-cipher-mismatch-in-google-chrome

Thanks , I have seen this and tried it but not working yet…tried to disable the universal ssl but still nothing works. Only when I pause cloudflare on the site I can access.

Hi,

I’m also a user of Siteground, and when they made their staging tool available to my hosting plan level I tried to implement it, but back then I concluded that it was not possible without un-proxying the staging subdomain.

Take the following with a pinch of salt, as this is my guess based on my attempts to make staging work, not their official word on this (you may want to check with their support). Their documentation says you need to have a DNS A record pointing to the staging subdomain, but I believe what they expect is that the A record point to your Siteground-assigned IP address, so their staging bot can know which of their servers hosts it.

When you add the staging subdomain as an A record in Cloudflare and set it to be proxied (:orange:), though you of course see your origin server IP address on the CF dashboard, visitors, including Siteground bots, will only see the Cloudflare-assigned IP address, not your origin IP address.

The only way I have been able to make Siteground staging work was by un-proxying (:grey:) the A record for the subdomain. But that has the following consequences:

  • all Cloudflare protections (WAF, Firewall Rules, Page Rules etc) as well as all performance enhancements (caching, image optmization if applicable, etc) are NOT applied to the subdomain; and
  • the IP address of your origin server is exposed.

For those reasons, I gave up their staging tool. As a turnaround, I use Softaculous to copy my WordPress installations into test. subdomains. Though not as good a solution as staging would be, it helps me test plugins, page layouts etc, before implementing them on the production site.

2 Likes

Hi,

Thanks for the feedback! It seems to be (finally) working when I put un-proxied the A record for the subdomain. Since this is a temporary staging environment I hope the things you listed will not effect much.

Thanks again!

1 Like

This topic was automatically closed after 30 days. New replies are no longer allowed.