I made 2 staging sites for www.Philsaviano.com and both of them have been inaccessible.
The main production site of philsaviano.com works fine and is using the Origin Certificate by Cloudflare because we wanted to enable DNSSec and the hosting company siteground - did not allow this. So their let’s encrypt ssl does not auto renew.
The Origin server uses both philsaviano.com and *.philsaviano.com.
When we created the staging sites, we added them as A records to the DNS file in Cloudflare.
Still could not access them properly - had to click several layers of warnings ie are you sure you want to view this potentially dangerous website…
After talking with siteground, and delaying cloudflare in order to set up Let’s encrypt ssl certs for at least one staging site (www.staging3.philsaviano.com), we were still able to view staging3 by going through the warnings. Siteground said to allow 24 hours for the changes to set.
Now more than 24 hours later, the staging site is completely unviewable.
This is the error:
ERR_SSL_VERSION_OR_CIPHER_MISMATCH … Unsupported protocol … The client and server don’t support a common SSL protocol version or cipher suite.
These tests failed in the diagnostic center:
Check for redirect loops
Check the HTTPS status
Check if redirecting unencrypted HTTP traffic works
Check the status of encrypted traffic
handshake_failure
Check the site for mixed content
Check site speed (TTFB)
Anyone with ideas about getting at least staging3 website to be viewable?
It’s that ‘www’ in front that’s causing this problem. I bet if your staging sites didn’t use ‘www’ in front of the subdomain, it’d work. More info here:
How would I use a non-www for the staging site? It’s created on the siteground server. The DNS record for staging3 is on cloudflare and I only used “staging3” and not “www.staging3” in the record.
I’ve greyed out the staging3 site and new error but still not displaying the site. Does this take a few - 24 hours to propagate the changes?
What I see is it trying to redirect to ‘www’ by your NGINX server. Somewhere in your configuration, it has a ‘www’ in front. A fuzzy memory of mine says that Siteground forces staging sites to have ‘www’ in front. Do you see any way to change that?
I bypassed using siteground’s account with cloudflare (which automatically assigns a www to the domain names when using their CF settings) and instead am using it manually, assigning server settings by CF at the domain registrar.
Again, because we couldn’t use dnssec.
I guess I’ll have to look at redirects from non-dub to www?