Support » Plugin: WooCommerce » Woo Commerce causing mixed content errors in Google URL inspection

  • Resolved ryansarn

    (@ryansarn)


    These errors appear on all pages of the website.
    When woo commerce is deactivated the errors do not appear, the errors are isolated to woo commerce.
    I believe this is seriously degrading my search rankings. I really need help! I have lost almost all organic search traffic.


    Warning
    00:08.557
    Mixed Content: The page at ‘https://bestsingingbowls.com/’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘http://bestsingingbowls.com/’. This content should also be served over HTTPS.
    https://bestsingingbowls.com/:0


    Warning
    00:08.558
    Mixed Content: The page at ‘https://bestsingingbowls.com/’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘http://bestsingingbowls.com/’. This content should also be served over HTTPS.
    https://bestsingingbowls.com/:0


    Error
    00:10.654
    XMLHttpRequest cannot load http://bestsingingbowls.com/. The request was redirected to ‘https://bestsingingbowls.com/’, which is disallowed for cross-origin requests that require preflight.
    https://bestsingingbowls.com/:0

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • ryansarn

    (@ryansarn)

    Possibly related:
    Word press would not update from v 5.2x to v 5.3x with woo commerce activated. I had to deactivate woo and then update WP and then woo. The site works fine – still with the same mixed content issue. I use Word Press Engine as my host. WP updated with woo activated in their staging environment.

    Plugin Support Rynald0s

    (@rynald0s)

    Automattic Happiness Engineer

    Hi @ryansarn!

    You can use https://wordpress.org/plugins/ssl-insecure-content-fixer/ to fix those warnings.

    Cheers!

    You will need to look a bit deeper. I already tried that before starting this ticket. The plug-in is currently installed and active.

    Plugin Support Three Sons

    (@3sonsdevelopment)

    Hi @ryansarn,

    I took a look at your site and ran a quick test to check for mixed content warnings.

    https://www.jitbit.com/sslcheck/

    It did not return any mixed content warnings and I don’t see any in the console either.

    console warnings

    Hopefully, that means you were able to get that error resolved. Let me know if you’re still seeing it.

    Best,

    Plugin Support Three Sons

    (@3sonsdevelopment)

    Hi @ryansarn,

    It’s been a while since I last heard from you so I’m going to close this thread out now. If you still have trouble, please open up a new topic and let us know.

    Best,

    ryansarn

    (@ryansarn)

    Hi 3 sons

    The lock is there and the SSL checkers come up clean. Whatever is happening urn off woo and google reports a clean site, turn it on and it has errors.

    One idea Google is picking up on references in woo to unsecure urls in redirection code.

    Plugin Support Three Sons

    (@3sonsdevelopment)

    Hi @ryansarn,

    I’d be happy to help you search for this more. Can you give us an example of the warning and specifically what it is showing as mixed content. That’s not typical of WooCommerce alone so we’ll to know specifically what’s being loaded only via HTTP to know how to address it.

    Cheers,

    Pasted above at the start are the error messages. We serve nothing as http. We’ve run scripts to search / replace all http, everything will come up clean in that regard, hence the lock on the site.

    My developer says the reason the robot is picking up http from the code is that it is written so that any http gets changed to https. In other words the part of the code that is being read is a redirection, not mixed content.

    He was able to hack out this code and get 2 of 3 google errors/warnings to go away. Hacking woo commerce core is NOT a solution.

    Plugin Support Three Sons

    (@3sonsdevelopment)

    Hey @ryansarn,

    My apologies…you did start with those. You mentioned these warnings going away when you disable WooCommerce. Have you tried with only WooCommerce and the Twenty Nineteen theme active? If you still run into errors with only WooCommerce and Twenty Nineteen active, then open up a bug report at GitHub.

    I haven’t been able to duplicate this on my test site, so the next step would be to test on your site with only those active. If the warnings aren’t present then it could mean there is a conflict with WooCommerce and either the theme or one of the other plugins. You could test further by enabling the theme and testing and then the other plugins.

    If you still have the warnings with only WooCommerce and the default theme, then fill in the information to create a bug report to let the developers know.

    Best,

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.