Site health – CURL Error 28 timeout

  • Resolved catacaustic

    (@catacaustic)


    1 year ago

    I’m having a problem with a site that shows site health errors for CURL – error 28. There’s a lot of “fixes” out there, but so far nothing has worked for me.

    To complicate matters, this is a dedicated VPS, and another WordPress site on the same server with the same settings does not have this error.

    The errors that show are:

    The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

    When testing the REST API, an error was encountered:

    REST API Endpoint: https://***/wp-json/wp/v2/types/post?context=edit
    REST API Response: (http_request_failed) cURL error 28: Connection timed out after 10001 milliseconds

    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: Connection timed out after 10001 milliseconds (http_request_failed)

    What I have done so far:

    • Disabled all plugins, set a Twenty* theme and deleted the .htaccess file
    • Checked that there is no firewall on the site or the server that’s blocking the requests
    • Checked SSL and DNS for any errors
    • Checked with the hosting companies server techs – and they can’t see any issues or configuration problems
    • Checked the REST URL in a browser, and it gets the expected “not allowed” response.

    As I said, this is very strange because the other site on the same server works fine and doesn’t have the same issue.

    So, is there anything else that I can check or any other ideas on what could be wrong with it?

Viewing 5 replies - 1 through 5 (of 5 total)
  • abletec

    (@abletec)

    1 year ago

    Hello, catacaustic, & welcome.

    Unfortunately, you don’t give us much to work with. We really need:

    1. 1) Your operating system;
    2. 2) The version of the operating system & WordPress;
    3. 3) The webserver you’re using;
    4. 4) The url of your site;

    There’s the possibility we’ll also need to look at any relevant configuration or .htaccess files. Logs are always a good way to troubleshoot these sorts of problems, so please check both error & webserver logs to see if they provide any insight.

    Thread Starter catacaustic

    (@catacaustic)

    1 year ago

    I can give some more info.

    The information that I can get from the phpinfo () is:

    System: Linux blhvps00013.**** 5.15.0-1030-aws #34~20.04.1-Ubuntu SMP Tue Jan 24 15:16:46 UTC 2023 x86_64

    Running WordPress 6.2 (but also was happening on 6.1).

    At this stage I can’t give the URL of the site.

    abletec

    (@abletec)

    1 year ago

    catacaustic, you didn’t include your webserver. Again, I strongly suggest having a look at your webserver & error logs to see what information they can provide. This is generally caused by a webserver &/or PHP misconfiguration as opposed to WordPress itself. It’s very difficult to assist when so little information is provided. I’m glad you’re being careful regarding what you post on public forums, of course, but at the same time, w/so little information present, it’s a bit like engaging in telepathy, which I personally failed miserably. I’m not a betting lady because I hate losing money, but if I were, I’d bet this comes down to a serverside problem as opposed to a problem w/the installation of WordPress. I have seen this problem quite a bit before, & I can’t recall an instance where that wasn’t the case.

    Again, if you could post some log entries relevant to the problem and tell us the webserver you’re running, we might be able to better assist. As I stated in a reply to a similar topic, this generally happens when the url being sought is somehow not being served. That can be due to PHP(fpm) misconfiguration or difficulties w/relevant configuration files. W/o knowing the webserver being used, it’s pretty hard to know what advice to give.

    Thread Starter catacaustic

    (@catacaustic)

    1 year ago

    For anyone else looking for this…

    @abletec was correct (as I thought that they would be). It turned out after much back-and-forth that the hosting company had some .htaccess rule(s) set up when they transferred the site across that I didn’t have access to that ended up blocking all CURL requests from any source. Once that was remembered and removed by the hosting techs everything started to flow smoothly again.

    At this stage no one can tell me why it just started happening when it did, but it’s fixed now so hopefully that will be it!

    abletec

    (@abletec)

    1 year ago

    Glad you got it resolved, catacaustic. Abletec (she/her/hers) :). Glad we could help. Best of success w/your new site.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Site health – CURL Error 28 timeout’ is closed to new replies.