Site Health: REST/loopback requests are failing, scheduled event failed

I’m sorry for the trouble @kadso . We’ll have this resolved in a future version.

Hi @michael ,

Is there any perspective as to when this update is going to be released?
I’m running into the same problem for multiple projects I’m working on.

Really liking DevKinsta so far, but this has been the only big downside for me.

Hi @Bob_van_de_Leur :wave: I’ve confirmed we do still have this listed on our side to be addressed, however I don’t have any type of ETA available, apologies. I understand the need to have that functioning properly and will certainly bump it with our development team. Hopefully we will have more news for you on that soon :crossed_fingers:

1 Like

Same here and its really pushes us to go back to MAMP…sad :frowning:

This issue “The REST API encountered an error…local port 443… your site coulnd not complete a loopback request” is still popping in my localhost’s wordpress site health.

I seek an update please…

I’m afraid no updates as of yet but I’ll be sure to post here as soon as we have more information on this.

1 Like

This (see quote below) is still very much a part of my every day reality. I seek an update. Please advise…

"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 7: Failed to connect to butterfly.local port 443: Connection refused (http_request_failed)"

Hi @kadso - I’m afraid at this time we don’t have an update to share yet on this issue. Thank you again for your patience on this.

Thank you Michael.

Anyone care to weigh in here an guide this non-programer where to look to find others where sooner rather than later timing is the working premise?

Hi Michael,

I’m still getting the two error messages below. What is the latest on resolving this topic?

  1. " 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 7: Failed to connect to butterfly.local port 443: Connection refused (http_request_failed)"

  1. 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 7: Failed to connect to butterfly.local port 443: Connection refused (http_request_failed)

No updates yet @kadso . I’ll be sure to share as soon as we have one!

Thank Michael. Can you loop me into what is the hold up?

@kadso I don’t have further information to share at the moment but will share here as soon as we do. Apologies again for the trouble.

Hi all

Any more information for this error on Dashboard on WordPress?

Thanks
Leonardo

Welcome to DevKinsta @binwebonlinesolution ! No updates yet to share at this time for this issue.

1 Like

I’m having the same issues. hope to have some update soon

Having the same issue. It has been almost 10 months since this was first reported – and still no solution? I am a bit worried about what problems this might cause for the sites. Would love some more information.

I’m sorry for the wait here. It depends exactly on the functionality of the site here, but in most cases it shouldn’t cause any major issues here. The error relates to making requests to itself.

Yes, the error relates to making requests to itself, which means any attempts to connect to any (custom) API endpoint will fail. So, it’s defintely a major issue.

I’m getting these messages in Site Health:

Unfortunately these prevent me from continuing my projects using DevKinsta, because I can’t connect to any of the APIs I created. (And they work fine in DevilBox – which is also a dockerized solution for creating local environments)

I’m curious, since I’m on Windows 10 Pro, and @slaFFik is also on Windows 10 Pro, is it a W10P specific issue?

Edit: it seems to be a specific issue for WordPress running in a Docker instance, I found these links. Maybe it’s a good idea to pass them on to your devs:

1 Like

HI everyone, I just want to report that DevKinsta v 2.6.0 has been released and addresses this issue! Please let us know if it is still occurring even after an update!