WP-Force-SSL does not work in Google Chrome

  • Resolved Douglas47

    (@douglas47)


    6 years ago

    I installed your WP-Force-SSL plugin, and it tested fine.

    If I input a generic http://www.site_name, or http://www.site_name into my browser, I will be redirected to my secure https:// site when using Internet Explorer, or Firefox. But in Google Chrome, it takes me to http://, and I get the circled “i” and “Not Secure.” Even if I type in https://site_name.

    Is this a common problem? Is there a fix?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Manuel Rocha

    (@manuelrocha88)

    6 years ago

    @douglas47 it would be great if you could provide the real domain… I cannot replicate the issue on my side with chrome… I need your real domain in order to check if i see something going wrong.

    Anyway, You should take in consideration that chrome shows sometimes the message near the domain with the word insecure but in the end is really using the https version. That happens when there is somewhere in the page a link pointing out to http instead of https. If that is the case you can use the service Why No Padlock in order to discover why. https://www.whynopadlock.com/

    Thread Starter Douglas47

    (@douglas47)

    6 years ago

    Hi Manuel. The domain is yoga-space.org, or, yogaconn.ehost.com/wordpress/

    I tried using chrome on another computer with the same result.

    I’ll try Why No Padlock right now, and let you know what happened.

    Thanks again for all your help.

    Thread Starter Douglas47

    (@douglas47)

    6 years ago

    Here is what Why No Padlock gave me:

    Tested URL

    https://yogaconn.ehost.come/wordpress/

    Test completed

    Fri, Jun 5, 2020 5:40 AM Eastern Time (GMT -5)

    Results URL

    https://www.whynopadlock.com/results/1574c44f﷓d1e9﷓4be4﷓90da﷓a82182782158

    SSL Connection – Errors

    The SSL certificate tests failed. Please be sure that you can connect to your site over SSL and try again.
    Mixed Content – Errors

    The Mixed content tests failed. Please be sure that you can connect to your site over SSL and try again.

    Error Returned: net::ERR_NAME_NOT_RESOLVED at https://yogaconn.ehost.come/wordpress/

    https://www.whynopadlock.com/results/1574c44f-d1e9-4be4-90da-a82182782158

    Thread Starter Douglas47

    (@douglas47)

    6 years ago

    Just as an added remark, my website, as seen by my users is yoga-space.org.

    I just tried whynopadlock using yoga-space.org and got the same results.

    So, then I used Internet Explorer, went to whynopadlock.com and got totally different results:

    Test Information

    Tested URL

    https://yogaconn.ehost.com/wordpress/

    Test completed

    Fri, Jun 5, 2020 5:54 AM Eastern Time (GMT -5)

    Results URL

    https://www.whynopadlock.com/results/743cdfce‑18a2‑4abd‑946e‑085dca695049

    SSL Connection – Pass

    SSL Certificate Info

    Certificate IssuerSectigo Limited Certificate TypeSectigo RSA Domain Validation Secure Server CA Issued On2019-03-26

    Force HTTPS

    Your webserver is not forcing the use of SSL.
    You may want to add a redirect to ensure a secure connection is used. More Info

    Valid Certificate

    Your SSL Certificate is installed correctly.

    Domain Matching

    Your SSL certificate matches your domain name!
    Protected Domains:
    *.ehost.com
    ehost.com

    Signature

    Your SSL certificate is using a sha256 signature!

    Expiration Date

    Your SSL certificate is current. Your SSL certificate expires in 387 days. (2021-06-27)

    Protocols

    You currently have TLSv1 enabled.
    This version of TLS is being phased out. This warning won’t break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018.

    Mixed Content – Errors

    Soft Failure

    An image with an insecure url of “http://yogaconn.ehost.com/wordpress/wp-content/uploads/2015/09/Logo.jpg” was loaded on line: 135 of https://yogaconn.ehost.com/wordpress/.

    This URL will need to be updated to use a secure URL for your padlock to return.

    Manuel Rocha

    (@manuelrocha88)

    6 years ago

    @douglas47 the ehost domain failed because you write down come instead of just com.

    Here is the correct check of the yogaconn.ehost.com: https://www.whynopadlock.com/results/dbc011a8-ccb1-4b9c-a4c9-2dfcd6d1c0f2

    I’m testing it on my chrome and your website is redirecting good on chrome. You probably are getting confuse because You are probably seeing like this:

    https://u.pcloud.link/publink/show?code=XZ7PI6kZ9iknvgRyWkJy9Ej5QlHzDfaAUzT7

    If you click right before yogaconn You will see it like this:

    https://u.pcloud.link/publink/show?code=XZXPI6kZdIcfn8L7yJVhk8qIgAjXnY0O8wsy

    The insecure word means there is some http left at the code. Looking at the chrome console I see this:

    https://u.pcloud.link/publink/show?code=XZMxI6kZHELCj3tsOJXXWNr5Xw2psQyUuOWk

    Which proves what I’m telling… There is some images that are still loading as http instead of https. Using our plugin only makes the website redirect from http to https, not the content itself.

    Fixing that on your code should fix it.

    The test engine from plugin is failing because, as you can see from why no padlock service, there is some TLS version outdated on your server that you should check with your provider.

    Thread Starter Douglas47

    (@douglas47)

    6 years ago

    Okay, my friend. Thank you so much for all your help. I’ll look through the code, change any http to https, and also ask my provider to update their TLS version. There is a light at the end of the tunnel!!!

    Manuel Rocha

    (@manuelrocha88)

    6 years ago

    @douglas47 great.

    If You haven’t done yet, and you have a minute, please leave a review. It’s what keeps support going. Thank you 🙏 https://ww.wp.xz.cn/support/plugin/wp-force-ssl/reviews/#new-post

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘WP-Force-SSL does not work in Google Chrome’ is closed to new replies.