SSL certificate verify failed
Problem is solved. It turns out that my web hotel had not installed the correct SSL certificate after all. I’m not excactly sure what they did or did wrong. But the problem is fixed.
Problem is solved. It turns out that my web hotel had not installed the correct SSL certificate after all. I’m not excactly sure what they did or did wrong. But the problem is fixed.
You better use a .htaccess file, where you force https with: RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301] The file goes in the root folder of your WP installation. If there is any, put this code on the beginning of the existing file. And you can then change the settings in the WP … Read more
SSL certificate error on Google Chrome , IE [closed]
wp_remote_get – curl error 28 connection timed out – using SANS in URL
I’d put the HTTPS redirect at the top of the htaccess file, not after the WordPress elements. See this page in the Codex for htaccess suggestions: https://codex.wordpress.org/htaccess . You need to redirect to https first before doing the WP rules in htaccess. You may also need to change any http to https in your database. … Read more
If you are doing this in .htaccess then I wouldn’t try to do this in a single redirect. The longest “chain” should be two redirects (1, 2 or even 3 redirects makes no difference for SEO): Canonicalise the HTTP to HTTPS and www to non-www in the first redirect Append the trailing slash in the … Read more
I solved it myself. You have to remove the stars in settings / stars. Afterwards the tool recognizes ssl and will load it from a secure version of the website.
You can use regular expressions in the server_name directive, but wildcard names (e.g. *.example.com) take precedence. See this document for details. For example: server { listen [::]:80 ipv6only=off; server_name ~^(www\.)?(?<name>(.+\.)?example\.com)$; return 301 https://$name$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; include snippets/ssl-example.com.conf; include snippets/ssl-params.conf; server_name ~^www\.(?<name>(.+\.)?example\.com)$; return 301 https://$name$request_uri; } server { listen … Read more
Is this the right set of records for Route53 domain to point to a mapped domain in a multisite? [closed]
I don’t think http and https would have matter, https is like a standard nowadays, in order to check properly, please try the following: Check your image link and make sure it is working Visit this FB debugger page – https://developers.facebook.com/tools/debug/ and check if something else is wrong.