Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1476746

    Good evening,
    I’m getting the error “Error accessing file for download: cURL error 28: Connection timeout after 10001 ms” when I try to download demo data. I have read through the posts and the documentation. I have –

    – Increased the timeout
    – Increased the memory
    – Attempted to install the demo data manually
    – Assigned a unique IP address to my server instance on my hosting provider (Dreamhost).
    – Used Cloudflare to proxy all the traffic
    – Installed WP manually instead of using the canned installation offered by Dreamhost.

    When a tracert is run from the server instance to kriesi.at, it is successful

    traceroute to kriesi.at (85.13.136.225), 30 hops max, 60 byte packets
    1 ip-173-236-240-1.dreamhost.com (173.236.240.1) 4.671 ms 4.587 ms
    4.543 ms
    2 * * *
    3 iad1-bdr-2.sd.dreamhost.com (208.113.156.194) 0.272 ms 0.261 ms
    0.253 ms
    4 be5698.rcr51.b037327-0.iad02.atlas.cogentco.com (38.122.62.253)
    0.955 ms 0.910 ms 0.870 ms
    5 be3562.ccr41.iad02.atlas.cogentco.com (154.54.24.233) 0.836 ms be3563.ccr42.iad02.atlas.cogentco.com (154.54.25.225) 1.015 ms be5698.rcr51.b037327-0.iad02.atlas.cogentco.com (38.122.62.253) 1.200 ms
    6 be3562.ccr41.iad02.atlas.cogentco.com (154.54.24.233) 0.967 ms
    0.845 ms *
    7 * 154.54.171.65 (154.54.171.65) 1.260 ms 1.417 ms
    8 be8073.ccr41.jfk02.atlas.cogentco.com (154.54.170.70) 99.869 ms
    99.687 ms be4188.ccr42.jfk02.atlas.cogentco.com (154.54.30.122) 92.931 ms
    9 be3627.ccr41.par01.atlas.cogentco.com (66.28.4.198) 90.022 ms be4188.ccr42.jfk02.atlas.cogentco.com (154.54.30.122) 93.143 ms be3472.ccr32.bos01.atlas.cogentco.com (154.54.46.33) 92.276 ms
    10 be3471.ccr31.bos01.atlas.cogentco.com (154.54.40.153) 93.198 ms be3685.ccr42.par01.atlas.cogentco.com (154.54.60.173) 88.854 ms be3393.ccr51.lhr01.atlas.cogentco.com (154.54.47.142) 92.670 ms
    11 be3393.ccr51.lhr01.atlas.cogentco.com (154.54.47.142) 96.670 ms
    96.982 ms be3684.ccr41.par01.atlas.cogentco.com (154.54.60.169) 93.381 ms
    12 be3684.ccr41.par01.atlas.cogentco.com (154.54.60.169) 93.238 ms be4975.ccr41.fra05.atlas.cogentco.com (154.54.63.69) 93.308 ms be3685.ccr42.par01.atlas.cogentco.com (154.54.60.173) 103.244 ms
    13 be6038.rcr71.nue01.atlas.cogentco.com (154.54.72.94) 96.653 ms be4975.ccr41.fra05.atlas.cogentco.com (154.54.63.69) 93.637 ms be5516.ccr21.muc03.atlas.cogentco.com (154.54.62.122) 97.980 ms
    14 be6038.rcr71.nue01.atlas.cogentco.com (154.54.72.94) 101.870 ms
    101.535 ms be5516.ccr21.muc03.atlas.cogentco.com (154.54.62.122) 97.954 ms
    15 dd16312.kasserver.com (85.13.136.225) 100.462 ms be6037.rcr71.nue01.atlas.cogentco.com (154.54.72.90) 105.649 ms be6036.rcr71.drs01.atlas.cogentco.com (154.54.72.85) 109.273 ms

    However, when I throw the curl command at kriesi.at, it fails

    curl -I https://kriesi.at/
    curl: (28) Failed to connect to kriesi.at port 443 after 130772 ms:
    Connection timed out

    Is it possible that your server is blocking the IP address or Dreamhost in general?

    Downloading the demo data does work on a WP instance that is NOT on my hosting provider; however, exporting the theme file consistently results in a TXT file, even after I add the entry define( ‘AVIA_GENERATE_DEMO_PHP_FILE’, true ) to the wp-config.php file. I will note a slight difference in the TXT file when the entry is present. The text inside the TXT starts with “$options = “. I tried renaming the file as a PHP, but the import stated the file was invalid.

    #1476789

    Forgot to mention, this is what I get when I throw curl at kriesi.at from a server that CAN download the demo data –

    HTTP/2 200
    vary: Accept-Encoding,Cookie,User-Agent
    cache-control: max-age=3, must-revalidate
    cache-control: max-age=608400
    expires: Sun, 16 Feb 2025 21:53:16 GMT
    x-cdn: Avia Media
    x-powered-by: Avia
    content-type: text/html; charset=UTF-8
    date: Sun, 09 Feb 2025 20:53:16 GMT
    server: Apache

    #1476799

    Hi,

    Thank you for the inquiry.

    The only known host so far having issues with the demo import is OVH, but it’s possible that restrictions on your server are causing the import to fail. If that is the case, you can try manually importing the demo by following these steps:

    — Download the demo that you’d like to install from this link: https://github.com/KriesiMedia/enfold-library/tree/master/demos

    — Extract the zip file and retrieve the XML file.

    — After that, go to Dashboard > Tools > Import and install the WordPress importer, then run it.

    — Upload the XML demo file.

    The demo images may not be included in the import due to server security restrictions. You can edit the pages and upload your own images.

    Let us know if this works.

    Best regards,
    Ismael

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