• Resolved Chad

    (@chadi)


    Hello,

    I installed your plugin and changed WP config (general settings) to https://www.chadiabizeid.com

    Now, in Firefox I get this:

    An error occurred during a connection to https://www.chadiabizeid.com. Cannot communicate securely with peer: no common encryption algorithm(s). Error code: SSL_ERROR_NO_CYPHER_OVERLAP

    Cleared cache. LetsEncrypt SSL is enabled on the domain already too. Using Cloudflare as well.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mark

    (@markwolters)

    Hi Chad,

    have you pressed the ‘Go ahead, activate SSL!’ button before changing your site address in the WP settings? This is something which Really Simple SSL normally does for you when pressing the activation button.

    The error you are seeing means that the browser and server cannot establish a cipher suite for a secure connection. In this case you can check the supported cipher suite for both your browser and server to see if there is a match. But on your site, visiting the https://www gives the cipher error, while visiting https:// works. Your chadiabizeid.com and https://www.chadiabizeid.com resolve to different IP addresses. One gives the error, and the other one doesn’t. This makes me thing it’s an issue with Cloudflare. I’ve done some searching and found a similar problem where the solution was to change the CNAME record from mydomain.cdn.cloudflare.com to mydomain.com. Could you try that to see if it works for you?

    Mark

    Thread Starter Chad

    (@chadi)

    @markwolters

    Thanks, but there is no “go ahead activate SSL” button anywhere in your plugin.

    I’ve disabled CF and confirmed CNAME is back to original. Your plugin is enabled and before I want to safely change WP & Site address to https://www.chadiabizeid.com instead of https://chadiabizeid.com.

    Plugin Author Mark

    (@markwolters)

    Hi Chad,

    when you first activate the plugin there should be a notice with the ‘Go ahead, activate SSL!’ button. It could be it didn’t appear because you set the site address to https://www manually, thus making Really Simple SSL see SSL is already activated. Both the www and non-www domain now point to the same IP address, you should be able to set the site address to https://www now.

    Mark

    • This reply was modified 7 years, 7 months ago by Mark.
    • This reply was modified 7 years, 7 months ago by Mark.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Blocked Now’ is closed to new replies.