cURL error 6: Could not resolve host

  • Resolved rafczy

    (@rafczy)


    1 month, 4 weeks ago

    Dear Staatic Team,

    I’m trying your plug-in and during the publishing I get the below error.

    It happens after some time, so part of my wordpress site gets converted.

    Crawl ‘MY_URL’ rejected (cURL error 6: Could not resolve host: my.host.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for MY_URL) (found on )

    To mitigate I set HTTP Concurrency setting to 1, but that didn’t work.

    Could you please help with this?

    Thank you

    ps MY_URL and my.host.com are just dummy values

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Team Staatic

    (@staatic)

    Hi @rafczy,

    Thanks for reaching out, and sorry to hear you’re having trouble. It sounds like your WordPress site is having difficulty resolving its own host, which Staatic relies on to generate the static version by crawling the site.

    Here are a few things you can try:

    1. Check Site Health: head over to WP-Admin > Tools > Site Health. Look for any issues or errors that might be causing the problem. Fixing these is probably enough to resolve this issue.
    2. DNS and hosts file: make sure your DNS settings are correct. You might need to add a DNS entry for my.host.com, or an entry in your /etc/hosts file to ensure it resolves correctly.
    3. Check security settings: sometimes, firewalls or security plugins can block internal requests. Try temporarily disabling them to see if that’s the issue.

    If none of these steps work, it would be helpful to check the Site Health info. You can get this by going to WP-Admin > Tools > Site Health > Info (tab) and clicking “Copy site info to clipboard”. You can send this info to us at [email protected], and we’ll take a closer look.

    Please let us know if this helps or if you have any other questions.

    Thread Starter rafczy

    (@rafczy)

    Thank you for responding. My site health looks pretty good. I suppose that is my hosting limitation, executing ulimit -u gave me 32 threads.

    Plugin Author Team Staatic

    (@staatic)

    hi @rafczy , thanks for the update. The error message indicates an issue with resolving the host, so it doesn’t seem related to the?ulimit. To help us investigate further, could you share your Site Health info?

    Alternatively, please check under the Site Health status to ensure that both “Your site can perform loopback requests” and “Staatic can perform loopback requests” are listed under Passed tests. These loopback requests are crucial for Staatic to function correctly.

    Looking forward to your feedback and helping you resolve this issue!

    Plugin Author Team Staatic

    (@staatic)

    The issue was confirmed to be due to resource limitations, which were addressed by adjusting concurrency settings and timeouts. Since there have been no further updates, we assume the solution worked.

    If similar issues arise, please don’t hesitate to reach out.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.