http://comments.gmane.org/gmane.comp.encryption.openssl.user/43587 suggests this one-liner: openssl crl2pkcs7 -nocrl -certfile CHAINED.pem | openssl pkcs7 -print_certs -text -noout It indeed worked for me, but I don’t understand the details so can’t say if there are any caveats. updated june 22: for openssl 1.1.1 and higher: a single-command answer can be found here serverfault.com/a/1079893 (openssl storeutl -noout -text -certs … Read more
The “challenge password” requested as part of the CSR generation, is different from the passphrase used to encrypt the secret key (requested at key generation time, or when a plaintext key is later encrypted – and then requested again each time the SSL-enabled service that uses it starts up). Here’s a key being generated, and … Read more
According to nginx pitfalls, it’s slightly better to omit the unnecessary capture, using $request_uri instead. In that case, append a question mark to prevent nginx from doubling any query args. server { listen 80; server_name signup.mysite.com; rewrite ^ https://$server_name$request_uri? permanent; }
In order to download the certificate, you need to use the client built into openssl like so: echo -n | openssl s_client -connect $HOST:$PORTNUMBER -servername $SERVERNAME \ | openssl x509 > /tmp/$SERVERNAME.cert That will save the certificate to /tmp/$SERVERNAME.cert. The -servername is used to select the correct certificate when multiple are presented, in the case … Read more
The [R] flag on its own is a 302 redirection (Moved Temporarily). If you really want people using the HTTPS version of your site (hint: you do), then you should be using [R=301] for a permanent redirect: RewriteEngine on RewriteCond %{SERVER_PORT} !^443$ RewriteRule ^/(.*) https://%{HTTP_HOST}/$1 [NC,R=301,L] A 301 keeps all your google-fu and hard-earned pageranks … Read more
You should be able to use OpenSSL for your purpose: echo | openssl s_client -showcerts -servername gnupg.org -connect gnupg.org:443 2>/dev/null | openssl x509 -inform pem -noout -text That command connects to the desired website and pipes the certificate in PEM format on to another openssl command that reads and parses the details. (Note that “redundant” … Read more
Your rewrite conditions, line 4 to 6 in your code, apply when https is active, so you are redirecting from https to https. Consquently you should change the conditions to check, if https is not active, ergo !on and !^443$ and !https. Additionally I’m not sure about the rule RewriteRule .* – [E=WPR_SSL:-https], probably something … Read more
Sounds like you switched over to HTTPS and your site assets aren’t loading. Here are a few things you can try. Update your site address by going to Admin > Settings > General and making sure you have https instead of just http in the URL fields Add define(‘FORCE_SSL_ADMIN’, true); to wp-config.php Change any static … Read more
You can disable the ssl verification by using ‘verify_ssl’ => false. So in your code you should change: [ ‘wp_api’ => true, ‘version’ => ‘wc/v3’, ‘sslverify’ => false, ] to: [ ‘wp_api’ => true, ‘version’ => ‘wc/v3’, ‘verify_ssl’ => false, ] Then you don’t need to change any source code.
You may have mixed content error at the site. Press ctrl+shift+i or right click and Inspect element. Click on console tab and check the warnings. If there is mixed content error, you can fix by changing the mixed content url at your files and database.