Guides No SSL detected SSL certificate Warnings & Errormessages

How to fix the ‘no response from webpage’ warning

Check if the front-end of your website loads

Does the front-end of your website load fine? Then this warning is a false positive and can be safely ignored. Does the front-end return a warning or error? Please follow the steps below to diagnose and fix the issue.

Check your SSL certificate

the no response from webpage notice shows when Really Simple SSL cannot load your homepage over SSL. This is often caused by a misconfiguration on the server or an invalid SSL certificate. The first step in fixing this message is to check if your site uses a valid SSL certificate. This can be tested with the Qualys SSL Labs test tool. This test will return a lot of information about the currently used SSL certificate, including any errors or misconfigurations. If the test returns a ‘T’ grade, then your site uses an invalid SSL certificate.

Really Simple SSL cannot obtain or install an SSL certificate for you. The plugin is a tool to configure your site for SSL and requires a valid SSL certificate before it can work correctly. If your site has an invalid SSL certificate we recommend to obtain a certificate at your hosting provider, they can help you install the certificate and is often the fastest and easiest solution. Once the certificate is valid, Really Simple SSL will be able to detect it and the warning should disappear.

Other possible causes

The Qualys SSL Labs test tool can also return different errors. For example, a ‘no secure protocols supported’ error. This error indicates that the server cannot be reached on port 443, the SSL port. This is often happens because of a misconfiguration on the server and can be fixed by your hosting provider.

On localhost environments, the cUrl request will return the following error:  cURL error 60: SSL certificate problem: unable to get local issuer certificate. This is normal and nothing to worry about if the front-end of your site works fine.

If you are unsure what to do next or have any questions in relation to this error, send us a support request.

Related Articles

Leave a Comment