REST API / Loopback request Issue

  • Resolved preclicked

    (@preclicked)


    5 years, 10 months ago

    Hey,

    I’m not sure if I should post this here or within the other plugin’s support page, but I can move it around if need be!

    I’m currently experiencing the issue found here: https://www.ads-software.com/support/topic/rest-api-unexpected-result/

    Another topic (https://www.ads-software.com/support/topic/rest-api-and-php/) also mentions the same error message and has now been marked as solved.

    From Marius L. J. (@clorith)’s closing comment, I believe a fix is going to be released with the next update of the Health Check plugin.

    ^^ That’s problem number 1 – But, I’m just mentioning it in case it’s related to problem number 2.

    When I install: https://www.ads-software.com/support/plugin/getresponse-integration and run Health Check, I get the following errors appearing:

    REST API availability >> The REST API request failed due to an error.
    Error encountered: (0) cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received

    A plugin has prevented updates by disabling
    wp_version_check()

    The loopback request to your site failed, this may prevent WP_Cron from working, along with theme and plugin editors.
    Error encountered: (0) cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received

    If I then click the ‘Run without plugins’ button, then ‘Test plugins individually’ – The only error reported is again from the GetResponse plugin and the error showing is:

    The loopback request to your site failed, this may prevent WP_Cron from working, along with theme and plugin editors.
    Error encountered: (0) cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received

    I’m well out of my depth here, but can follow instructions pretty well ??

    Any help is much appreciated!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    So the two are not related (phew, it’s been a long week).

    It sounds like the GetResponse plugin is doing something that blocks the loopbacks, I’m not familiar with their plugin, but I would definitely reach out to them and let them know that something there is blocking them.

    The bit about something blocking automatic updates may well be your host, many hosts will apply the updates for you, and therefore disable that feature in WordPress ti self, we may well see this report change moving forward if hosts are able to interact and mark it as working when they do the updates (that’s a hopeful end from my side, and not something actively pursued at this time). So if your site is getting updates like it should, you don’t need to worry about that bit, but loopbacks being prevented, if your host isn’t updating your site, may affect auto updates, so do get that looked at!

    Thread Starter preclicked

    (@preclicked)

    Hey,

    Many thanks for your response and for helping separate the two issues better.

    I’ll take your advice and see if the GetResponse team are able to provide any suggestions or can have a look into it. For now, I’ve removed the plugin and added the form through an HTML block instead so I’m happy with my workaround and use one less plugin, too.

    After rerunning Health check, (with your latest update ((many thanks again!! :D))) – The results are much better and the only ones that remain are the outdated PHP module thing, that I see in the other topic is still on the to-do list.

    RE: The auto updates – I have them turned on but strangely the error only show with the GetResponse plugin turned on?

    Another odd one, but I think I can live without the plugin anyway, so it’s not bugging me as much now.

    I will see if my host can do anything about the loopback part on their end, though.

    Many thanks again for your help! ??

    • This reply was modified 5 years, 10 months ago by preclicked.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘REST API / Loopback request Issue’ is closed to new replies.