cURL Error 28 by WP Wham’s Currency Switcher – Security Update is Essential

Hi there, I am getting the same errors in the WP Site Health check. I have disabled all other plugins then reenabled one by one and it is the Currency Switcher plugin causing the critical warnings. Could you please check and update for compatibility with the latest WP version?

The Rest API encountered and error
Your Site could not complete a loopback request

Thanks!

This is not a security issue. cURL Error 28 simply means the connection timed out. For information about this error, the following page may be helpful: https://docs.presscustomizr.com/article/326-how-to-fix-a-curl-error-28-connection-timed-out-in-wordpress

If you need further assistance please open a support ticket here: https://wpwham.com/support/.

Best regards,
David

I just posted about same problem — in my case REST API are also not working.

Problem follows the plugin. Disabling plugin fixes the issue.

Rudolf

hello I also have the same problem with your plugin its damage I like simple and light plugin and I had it well integrated into my theme but I will be forced to remove it if I find no solution
———–
The REST API is one way WordPress, and other applications, communicate with the server. One example is the block editor screen, which relies on this to display, and save, your posts and pages.

The REST API request failed due to an error.
Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)
————
Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

The loopback request to your site failed, this means features relying on them are not currently working as expected.
Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)
———–
Background updates ensure that WordPress can auto-update if a security update is released for the version you are currently using.

Warning Could not confirm that the wp_version_check() filter is available.

As I said on the other thread, this is not a defect with our plugin. If you are referring to WP’s healthcheck messages, it is a known bug in WordPress. Aside from the Healthcheck message, there is no interference with the normal functioning of your website.

The WP Team have a fix slated for version 5.5. We are waiting for WordPress to release the fix.

If you need further support please open a support ticket. We do not monitor this forum.