Geek Answers Handbook

SSL privacy error with Wpengine staging sites

We have set up an intermediate site with Wpengine, and since the Wordpress 4.0 update all pages requiring SSL have refused to connect.

Error in Chrome:

Your connection is not private. Attackers may try to steal your information from your .staging.wpengine.com website (for example, passwords, messages or credit cards).

Error in Firefox:

This connection is not trusted. You asked Firefox to connect securely at your-site.staging.wpengine.com, but we cannot confirm that your connection is secure. Usually, when you try to connect securely, sites will present a trusted identity to prove that you are going to the right place. However, this site identifier cannot be verified.

Does anyone else encounter the same problem or find a workaround? In Chrome, you can click Advanced> Continue and see the site with SSL errors only.

+4
source share
3 answers

Doyle Lewis has the correct answer , you see errors, because the domain on which your site is hosted does not have a signed SSL certificate.

When you use the WP Engine service, your site is mirrored in the temporary domain provided by WP Engine. Most likely, what happens here is that your site requires an SSL certificate, and the one that it expects will be for your regular domain (not "your-site.staging.wpengine.com").

, , "" > "", .

, . , WP Engine, , .

+1

.

.

.

"*.wpengine.com".

URL-:.staging.wpengine.com

, , , "*.staging.wpengine.com".

0

The intermediate site is not designed to test your SSL, because you are at an intermediate address where you have zero SSL control, because it is owned by WP Engine, and you do not have a true way to enforce it. This procedure is for troubleshooting and theme development.

0
source

More articles:


All Articles