Getting Curl Timeout error

  • Hi Dinesh,
    I am having an issue with license Activation.
    I am getting a curl Timeout error. Event though there’s no such limitation on my server.

    I have verified your ip isn’t blocked by my servers or limited in any matter.

    cURL error 28: Connection timeout after 10001 ms

    Can you please check on the issue.

    cURL error 28: Connection timeout after 10001 ms

    I am adding licesnse information and status directly into database until it’s fixed.

    Thanks In advance.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Dnesscarkey

    (@dnesscarkey)

    Hi @hasaanch,

    Thanks for reaching out. Could you check if your server can make a cURL request to dineshkarki.com.np? wanted to ensure there are no security measures or firewall rules blocking the connection, as these can sometimes interfere with license activation. May be you can ask your hosting provider to check on this.

    Best,
    Dinesh

    Thread Starter Hasaanch

    (@hasaanch)

    Hi Dinesh,
    Thanks for your speedy reply.

    I checked doing Curl to your domain and it’s giving timeout, where on my local machine it’s doing on the spot.

    I manage the server on my own, I am using Plesk. I am using Fail2Ban only and I checked it and your ip is not in the blacklist. I even added it to whitelist but still timeout.

    Is it possible that my server IP might be blocked from your end?

    Let me know if it’s possible, I will send you my IP Address to check.

    Plugin Author Dnesscarkey

    (@dnesscarkey)

    Thanks for checking. I’ve also reviewed our IP blacklist, and there are no blocked IPs on our end. Based on past cases, some server settings can cause this issue, especially if the license activation page reloads without any error message.

    Here are a few things you might want to check:

    1. CDN Settings: If you’re using a CDN, try disabling it temporarily. Some users have reported that disabling the OVH CDN resolved similar issues.
    2. Firewall & Security Settings: Even if Fail2Ban isn’t blocking our IP, other security layers (like ModSecurity or Imunify360) might be interfering with external requests. It could be worth checking their logs.
    3. Cloudflare & Caching: If Cloudflare is enabled, try:
      • Clearing the cache for the domain and verification endpoint.
      • Disabling Edge Cache TTL or setting it to a low value to avoid caching security pages.

    Let me know if any of these help.

    Best,

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