Title: Loopback and reset API error Last modified: July 6, 2020 --- # Loopback and reset API error * Resolved [creative024](https://wordpress.org/support/users/creative024/) * (@creative024) * [5 years, 11 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/) * After hours of testing I have narrowed my issue down to this plugin causing the errors. * The error only shows when 2 plugins are activated. Stock theme and no other plugins are activated and I get this error. * I have the pro-version of this plugin. * ———- * The REST API encountered an error Performance 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) * _________ * Your site could not complete a loopback request Performance 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) Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Author [Jurski](https://wordpress.org/support/users/jurski/) * (@jurski) * [5 years, 11 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13092171) * Thank you for bringing this to our attention, however, we would need to know more detailed information about the hosting platform to see if there is anything we can do to troubleshoot it further. * On the various platforms we tested, we could not re-create the error. However, when dealing with curl and the REST API, the hosting platform must be configured correctly for both security and accessibility. * For example, you mentioned (http_request_failed) which is an insecure request. Per Google’s map API restrictions, they require us to use SSL which would also be https requests to curl and the REST API. * Previously browsers and servers would warn of insecure connections, but depending on the hosting platform, they may now require it. * You may have to check with your hosting provider to be sure that is all correctly configured, but the first thing to check is if your site can be run in https SSL. * [belfieldfurnishings](https://wordpress.org/support/users/belfieldfurnishings/) * (@belfieldfurnishings) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13304974) * Hello there * I have had exactly the same issue. I have my hosting through 123 reg. I was wondering if there was a conclusion to this problem? * Thread Starter [creative024](https://wordpress.org/support/users/creative024/) * (@creative024) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13305146) * Unfortunately for me they have stopped responding to questions. I think I have it narrowed down to the PHP version the server is running but they have not gotten back to me. I have the issue on 2 websites on 2 different servers running php 7.4 and 7.3 I am looking for other solutions. * [belfieldfurnishings](https://wordpress.org/support/users/belfieldfurnishings/) * (@belfieldfurnishings) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13305181) * I’ve got an idea, I’m going to roll back my PHP version and see what happens. In the development environment I was using the php was 5.2, so I know I can roll back fairly safely just to get through the launch and maybe apply a more permanent fix at the end of the week. * Thread Starter [creative024](https://wordpress.org/support/users/creative024/) * (@creative024) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13305190) * I think it works with 5.2, please let us know. * [belfieldfurnishings](https://wordpress.org/support/users/belfieldfurnishings/) * (@belfieldfurnishings) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13305338) * The furthest I could go back is 5.6 and that has cleared up the issue and slightly sped up the site. It appears to be a PHP 7 issue. I feel like there will be more ground to be gained by investigating the SSL further too. I’ll let you know if I come up with something solid. * Plugin Author [Jurski](https://wordpress.org/support/users/jurski/) * (@jurski) * [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13313511) * [@belfieldfurnishings](https://wordpress.org/support/users/belfieldfurnishings/) Can you please confirm if the issue you had was on PHP 7.4 and PHP 7.3? * Also, can you confirm you are running all requests in https? * Please send an email to support @ vitalorganizer dot com and we can start a support ticket into this. Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Loopback and reset API error’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/vo-locator-the-wp-store-locator_a4dae2. svg) * [VO Store Locator - WP Store Locator Plugin](https://wordpress.org/plugins/vo-locator-the-wp-store-locator/) * [Frequently Asked Questions](https://wordpress.org/plugins/vo-locator-the-wp-store-locator/#faq) * [Support Threads](https://wordpress.org/support/plugin/vo-locator-the-wp-store-locator/) * [Active Topics](https://wordpress.org/support/plugin/vo-locator-the-wp-store-locator/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/vo-locator-the-wp-store-locator/unresolved/) * [Reviews](https://wordpress.org/support/plugin/vo-locator-the-wp-store-locator/reviews/) * 7 replies * 3 participants * Last reply from: [Jurski](https://wordpress.org/support/users/jurski/) * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/loopback-and-reset-api-error/#post-13313511) * Status: resolved