SSL issues and errors can occur for a variety of reasons. Below you can find information on troubleshooting some of the most common ones.
Invalid or No SSL Certificate
If your site has an invalid or no SSL certificate, you will be presented with an error such as this when you attempt to visit your site:
Every site hosted with Pressable is provisioned with its own SSL certificate. However, if a domain is added to a site before the DNS has been pointed to us, we won’t be able to provision the certificate. The first step to resolving this is to make sure your DNS settings have been set up correctly as detailed in this guide.
Once the DNS settings have fully propagated, you can use the “Retry SSL” button on your site’s page in your My Pressable Control Panel:
Doing this will attempt to reprovision the SSL certificate for your domain and show “Retry SSL Pending” while the system works on this. The process is normally very quick, and it is easy to confirm if the problem has been resolved. If “Retry SSL Pending” reverts back to the “Retry SSL” button, your DNS settings may not have propagated yet, meaning we still can’t provision the SSL certificate. If “Retry SSL Pending” is replaced with nothing, then the process was successful.
You should then confirm this by visiting your site to ensure the error message there has also gone away. Make sure you clear your browser cache before doing this, as you can sometimes have the old version cached in your browser which will still show the SSL error.
Mixed Content Warnings
For SSL to work properly, all content that is used on the site must be served over HTTPS, i.e. a link which uses https://. If your site has links that use http:// you may see that there is no padlock showing beside the URL in your address bar or it may show “Connection is not secure”. There will also be errors like this showing in your browser’s developer console:
The best way to ensure that you catch all insecure links on your site is to perform a search-replace for http:// to https://. You can find more information on this in our Search & Replace article.
Once the search-replace has been performed, these error messages should no longer be present and your site should show as secure again.
If after this you are still seeing Mixed Content warnings, the insecure links may be hardcoded somewhere, such as in your theme’s css file. This will mean accessing that file via SFTP and manually updating the link(s).
If you are still experiencing SSL issues after following the steps in this guide, get in touch with support at firstname.lastname@example.org and we’ll be happy to assist.