No SSL detected Warnings & Errormessages

No SSL detected, but I’m sure I have SSL

No SSL was detected

If you see this message at the top of your page, this can mean two things:

  • You don’t have an SSL certificate. You can check this on
  • The certificate check in Really Simple SSL failed, because the output on yours server differs from the expected output.

If the scan on SSL Labs checks out, you can get Really Simple SSL to detect SSL simply by loading the admin over SSL:

  1. Go to the login page of your site on https, e.g.:, and login
  2. Your site layout might break, but don’t worry. This is because the stylesheets are not SSL yet.
  3. Look for the button “enable SSL” (you might have to scroll down a bit if it’s broken), and click it.

That’s it! Your site will now be configured for SSL.

An alternative method, if the above does not work, is to force the plugin to activate by adding

define(“RSSSL_FORCE_ACTIVATE”, true);

to your wp-config.php. Please note that if your site does not load properly over https because of server configuration issues, this might cause problems. Be careful with this option.

If SSL was detected, but you’re seeing this message after activation: to change this page upload a new index.html to your private_html folder or something similar, pease check out the link for the article on this topic.

Edge case: test page couldn’t be opened and no server variables

There are some cases in which the test page could not be opened by the plugin, and when you check it manually:

It returns this:


(make sure you have https in the url!)

In these cases, even if you load your site over https, it will still return “no SSL detected”. In that case, you need to “force” WordPress to see it is on SSL. You can do this by adding

$_SERVER[“https”] = “on”;

To your wp-config.php. Normally Really Simple SSL does this, but if the testpage couldn’t be opened, it won’t do this automatically.

Related Articles

  • Amp javascript warning with Really Simple SSL

    If your site uses AMP (accelerated mobile pages) in combination with Really Simple SSL, you might encounter an error regarding javascript in the head of the website. If you see...
  • err_ssl_protocol_error

    err_ssl_protocol_error The err_ssl_protocol_error is usually caused by a failure to securely communicate with the server and often has to do with the server configuration. For any SSL related error there...
  • How to solve a http 500 error on activation of Really Simple SSL

    When you have white screen, or a http error when activation Really Simple SSL, this can have two causes: your site is low on memory, or there’s a plugin conflicting...

    ERR_SSL_VERSION_INTERFERENCE The ERR_SSL_VERSION_INTERFERENCE is an SSL related error that usually appears in Google Chrome and Firefox when a site (server) uses TLS1.3. The err_ssl_version_interference error can be solved in a...


  • Richard

    I tested:
    SSL test page

    This page is used purely to test for ssl availability.



    REQUEST_URI: /wp-content/plugins/really-simple-ssl/ssl-test-page.php

    When i add the code to .htaccess, the

    500 internal server error problem is coming.

    • Rogier Lankhorst

      The article was a bit out of date. I’ve updated it: the best way to solve this is to change the url in your browser bar to https (when you’re in the admin), then hit enter.

      • Stanly

        I’m struggling with the same issue. Earlier, SSL was working perfectly for me. But I had disabled for some reason. Now when I activated again, I’m not able to fix this issue at all. I’ve tried all the methods (adding in wp-config.php and trying with https://…) given here. Can you please help me?

        • Rogier Lankhorst

          What happens when you login over the https url?

  • barbara gustafson

    Thanks for the tip. Worked like a dream. Love the ease of use of the product.

  • William Muriuki


    The plugin also did not detect my SSL certificate and I am sure I have one and i have tested it on the recommended site (and gotten an A)
    When I try to reload the admin via https:// manually it reports a 404 error that the page does not exist.
    What can I do?
    Please help

  • Raj

    I’m having the same problem where I get the “No SSL detected” message.

    I run my site through SSL checker site and get all A’s

    I setup the free flexible SSL you get with CloudFlare about 2 hours ago. It shows as Active within CloudFlare.

    When I try to go to my wp-admin page via https I get “Not Secure” in the url bar and the page shows the standard “Your connection is not secure” message.

    What can I do to resolve this?

    • Rogier Lankhorst

      Do you see the “go ahead, activate SSL” button when you load the admin over https? If so, you can click it to enable SSL. If the styling breaks you might need to scroll down a bit.

  • Loren Noble

    All the same issues and when I load admin over https there is no option to activate SSL button. What other option is there. I have done everything mentioned here. Mine also used to work.

    • Rogier Lankhorst

      What is the domain you have the issue on? If there are no server variables WordPress can use to decide if it’s on SSL, it might help if you add
      $_SERVER[“https”] = “on”;
      To your wp-config.php

    • Mark Wolters

      Hi Hans,

      do you normally have any redirects on your site? What path does the redirect checker ( show? You could check if any page rules are set-up in Cloudflare which might perform this redirect. It could be a .htaccess rule which triggers on a https:// visit or a redirection plugin. It’s hard to say without access to your site. You can check these options to see if one of them is responsible for the redirect. If you are still unsure you can send us WordPress and FTP login details through so we can have a look.


  • edd_user_5476568

    Hi Hans,
    I’m having a similar problem. The Really Simple cannot detect the ssl certificate and when I load from the admin as suggested, I get this error: “This site is not accessible”.

    • Mark Wolters


      can you provide me with your site address? Does your site have a valid SSL certificate? You can test your certificate here: Really Simple SSL requires a valid certificate before it can work correctly.


      • edd_user_5476568

        my site address is

        I have the certificate installed on four sites in total and isn’t working on none of the four sites.

        I Have followed the instructions as you have suggested using the code in the config.php to force the activation and it hasn’t work neither.

        • Mark Wolters

          there seems to be an issue with the server configuration, the server cannot load over port 443, the SSL port. This can be fixed by your hosting provider by opening port 443. Once port 443 is opened and a valid SSL certificate is installed, Really Simple SSL will help to convert your site to SSL.

          • edd_user_5476568

            Thank you, I will get in touch with my hosting company to see if they can help solve this issue.

  • Muhammad Mohsin Raza

    Let’s Encrypt certificates have been installed by my hosting provider and I’ve checked it on and got A but this plugin is showing that

    Really Simple SSL failed to detect a valid SSL certificate. If you do have an SSL certificate, try to reload this page over https by clicking this button:

    but when I reload the page with https nothing happened. Moreover when I updated url from http to https in wp-options table in database the website shows the error “This page isn’t working, ERR_TOO_MANY_REDIRECTS” .
    I don’t know what to do as I’ve tried every possible way found on google.
    waiting for your response

    • Rogier Lankhorst

      Can you try to change the URL in the browser address bar to https, then hit enter? This will enable the plugin to detect SSL.

      • Muhammad Mohsin Raza

        Yes I did so but it shows the “This page isn’t working” ERR_TOO_MANY_REDIRECTS”

          • Muhammad Mohsin Raza

            article did not helped me… I’ve disabled all the themes and plugins by renaming these folders through “ftp” and I also have replaced all http to https in database through phpmyadmin and still now I’m getting the same error
            “This page isn’t working redirected you too many times.
            Try clearing your cookies.
            the hosting has provided me plesk panel and I also can not locate ssl certificates in root folder of website. When I asked hosting provider to place ssl certificates in root folder he denied to do so due to security risk…. can you please guide me what can I do or I’ve to shift back to http….

          • Mark Wolters


            have you also checked the .htaccess and wp-config.php files for any http:// references? There must be something forcing your site over http://.

        • Rogier Lankhorst

          Did you try the edge case scenario described in this article? In some cases, you might need to add $_SERVER[”https”]=”on”; to your wp-config.php. If you still have issues, please post it on the support forum, or submit a ticket, as the comment system is not really meant for such extensive discussions.

  • crossed

    Hi, I am having this issue and still can’t figure it out. I tried SSL Labs shows a valid ‘A’ certificate. When I try to reload the site under https I get “Not Found [CFN #0005].” When I try to just load the secure version of the site I get a slightly different error, “Not Authorized to View This Page [CFN #0004].” Even though I can’t get the site to load over https, i still tried some manual configuration changes to the wp-confic.php file, including the RSSSL_FORCE_ACTIVATE one, but it didn’t fix it. The site is Any ideas?

    • Mark Wolters


      This is likely caused by a misconfiguration on your webserver. We recommend to contact your hosting provider about this issue. They can locate and fix the cause of this error. Once this has been fixed, Really Simple SSL will be able to detect your SSL certificate.


      • crossed

        Hi Mark,

        Thanks for the quick reply. I contacted them first and they said everything was set up correctly on their end. They told me I needed to fix the issue in wordpress by “updating the code.” I asked for specific steps and they said they were “not coders” so they didn’t know. But they assured me everything was correct on their end. I’m not sure I believe them. I’ve tried a half dozen different changes including attempting to force https for admin login, but nothing seems to be working. Is there by chance a way I can figure out exactly what they need to change with the web server so I can have a more specific ask next time I contact them? This is unfortunately my client’s hosting company, or I would switch in a heartbeat to a better one. I have noticed I am unable to connect using the secure ftp port, only the standard one. Do you think that has anything to do with it?

        • Mark Wolters

          Possibly the site uses two different folders for http:// and https://, a public folder for http:// and a private/public folder for https://. If the contents of these folders don’t match, the https:// domain can give an error like this. Usually this can be fixed by creating a symbolic link between the two folders.

Leave a Comment