WooCommerce’s Background Processing Test fails with:
“Could not connect. Please ask your hosting company to ensure your server has loopback connections enabled.”
I am using the Meta for WooCommerce plugin, and product synchronization to Meta Commerce Manager is not working.
Meta/WooCommerce connection itself appears to work, and Meta API requests return HTTP 200, but the WooCommerce catalog synchronization does not upload any products.
Could you please check whether server-to-self HTTP/HTTPS loopback requests are supported for my hosting account/domain?
In particular, could you check whether requests from:
back to itself, including WordPress background requests such as wp-cron.php and admin-ajax.php, are being blocked by the hosting environment, firewall, security system, or other restrictions?
Your site should be able to collect to itself. And it can connect out to woo commerce servers. What it can’t do is let woo commerce checks connect to your site because the security system blocks bots ect
What you’re describing is somewhat covered by these articles:
In short: any connections to your website that’s not from a browser will not work. This includes WordPress’ own loopback connections, as well as any API calls or webhooks to your website (API access from your website to other providers, like Meta, do work).
WordPress cron jobs can be run using regular WP Cron, which runs some background tasks alongside regular web requests, If you need to help the cron along for some reason, you can just trigger it directly by opening the URL https://clickmart45.kesug.com/wp-cron.php in your browser.
For most websites, this is not a big issue, and WordPress cron updates getting stuck is usually caused by bad jobs blocking the queue, not by lacking cron job or loopback request support.
But this applies mainly to vanilla WordPress. WooCommerce is a much more complicated beast, and so are the wealth of plugins on top of it to integrate with external marketplaces, which may have their own dependencies and complications.
All in all, I’m 70% sure that the error you’re seeing is a red herring and doesn’t actually impact your website. But I’m no WooCommerce expert so I’m not completely sure.