Array ( [11] => Array ( [pid] => 50318419 [fid] => 135 [tid] => 635368 [first] => 0 [author] => greenteas [authorid] => 75884 [subject] => [dateline] => 1730476426 [message] => i think the files are too big, not everybody has the super internet connection it would be better to limit the MB, maybe up to 30 or 35 MB [useip] => 91.49.127.110 [port] => 59254 [invisible] => 0 [anonymous] => 0 [usesig] => 1 [htmlon] => 0 [bbcodeoff] => -1 [smileyoff] => -1 [parseurloff] => 0 [attachment] => 0 [rate] => 0 [ratetimes] => 0 [status] => 0 [tags] => 0 [comment] => 0 [replycredit] => 0 [position] => 11 ) [12] => Array ( [pid] => 50324937 [fid] => 135 [tid] => 635368 [first] => 0 [author] => Wooggins [authorid] => 346012 [subject] => [dateline] => 1730508058 [message] => I'm having this issue with compressed files - pdf files take about 20 seconds. [useip] => 172.71.254.109 [port] => 19776 [invisible] => 0 [anonymous] => 0 [usesig] => 0 [htmlon] => 0 [bbcodeoff] => -1 [smileyoff] => -1 [parseurloff] => 0 [attachment] => 0 [rate] => 0 [ratetimes] => 0 [status] => 0 [tags] => 0 [comment] => 0 [replycredit] => 0 [position] => 12 ) [13] => Array ( [pid] => 50380527 [fid] => 135 [tid] => 635368 [first] => 0 [author] => knitknitknit [authorid] => 157540 [subject] => [dateline] => 1730749070 [message] => Cloudflare issue continues... Have not been able to download these files after dozens of attempts: Knit Now - Issue 174 - Practical Publishing 2024 [url]www.pindiy.com/forum.php?mod=viewthread&tid=637846&fromuid=157540[/url] size 79.43 MB The Muness Shawl by Sharon Miller - Heirloom Knitting [url]www.pindiy.com/forum.php?mod=viewthread&tid=638094&fromuid=15754[/url] size 26.67 MB Update:This one finally popped up download! Very frustrating trying to keep track of what you paid for and received and what keeps failing to download. Also noticing pages don't load all at once, a partial page shows with blank space then it stutters loading the rest. Buffering server seems to not have enough resources. https ://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred Error 524: a timeout occurred: Error 524 usually indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second Proxy Read Timeout. This can happen if the origin server is taking too long because it has too much work to do - e.g. a large data query, or because the server is struggling for resources and cannot return any data in time. Error 524 can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 second Proxy Write Timeout. Note A 524 occurs if the origin web server acknowledges (ACK) the resource request after the connection has been established, but does not send a timely response. Resolution Here are the options we’d suggest to work around this issue: Implement status polling of large HTTP processes to avoid hitting this error. Contact your hosting provider to exclude the following common causes at your origin web server: A long-running process on the origin web server. An overloaded origin web server. Note Logging request response time at your origin web server helps identify the cause of resource slowness. Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as Apache ↗ or Nginx ↗. Enterprise customers can increase the 524 timeout up to 6,000 seconds using the Edit zone setting endpoint (proxy_read_timeout setting). If your content can be cached, you may also choose to use a Cache Rule with the Proxy Read Timeout setting selected instead in the Cloudflare Dashboard. Note If the timeouts are on write requests, the Proxy Write Timeout of 30 seconds cannot be adjusted. If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain not proxied (grey clouded) in the Cloudflare DNS app. Note Please note that you may observe a 1 second difference between the timeout you’ve set and the actual time at which the Error 524 is returned. This is expected, it’s due to the current work on implementing Pingora, our new proxy ↗. As a workaround you can simply set the timeout to 1 second more (121 seconds instead of 120 seconds for example). [useip] => 107.77.204.229 [port] => 37096 [invisible] => 0 [anonymous] => 0 [usesig] => 1 [htmlon] => 0 [bbcodeoff] => 0 [smileyoff] => -1 [parseurloff] => 0 [attachment] => 0 [rate] => 0 [ratetimes] => 0 [status] => 0 [tags] => 0 [comment] => 0 [replycredit] => 0 [position] => 13 ) ) Timeouts can\'t download-Cant Download attachment (and reply)-Recycled-PinDIY.com - Powered by Discuz! Archiver

greenteas Publish time 2024-11-1 23:53

i think the files are too big,
not everybody has the super internet connection
it would be better to limit the MB,
maybe up to 30 or 35 MB

Wooggins Publish time 2024-11-2 08:40

I'm having this issue with compressed files - pdf files take about 20 seconds.

knitknitknit Publish time 2024-11-5 03:37

Cloudflare issue continues...

Have not been able to download these files after dozens of attempts:

Knit Now - Issue 174 - Practical Publishing 2024
www.pindiy.com/forum.php?mod=viewthread&tid=637846&fromuid=157540

size 79.43 MB

The Muness Shawl by Sharon Miller - Heirloom Knitting
www.pindiy.com/forum.php?mod=viewthread&tid=638094&fromuid=15754

size 26.67 MB
Update:This one finally popped up download!

Very frustrating trying to keep track of what you paid for and received and what keeps failing to download.

Also noticing pages don't load all at once, a partial page shows with blank space then it stutters loading the rest.

Buffering server seems to not have enough resources.

https ://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred

Error 524: a timeout occurred:

Error 524 usually indicates that Cloudflare successfully connected to the origin web server, but the origin did not provide an HTTP response before the default 100 second Proxy Read Timeout. This can happen if the origin server is taking too long because it has too much work to do - e.g. a large data query, or because the server is struggling for resources and cannot return any data in time.

Error 524 can also indicate that Cloudflare successfully connected to the origin web server to write data, but the write did not complete before the 30 second Proxy Write Timeout.

Note

A 524 occurs if the origin web server acknowledges (ACK) the resource request after the connection has been established, but does not send a timely response.

Resolution

Here are the options we’d suggest to work around this issue:

    Implement status polling of large HTTP processes to avoid hitting this error.
    Contact your hosting provider to exclude the following common causes at your origin web server:
      A long-running process on the origin web server.
      An overloaded origin web server.

Note

Logging request response time at your origin web server helps identify the cause of resource slowness. Contact your hosting provider or site administrator for assistance in adjusting log formats or search for related logging documentation for your brand of web server such as Apache ↗ or Nginx ↗.

Enterprise customers can increase the 524 timeout up to 6,000 seconds using the Edit zone setting endpoint (proxy_read_timeout setting). If your content can be cached, you may also choose to use a Cache Rule with the Proxy Read Timeout setting selected instead in the Cloudflare Dashboard.

Note

If the timeouts are on write requests, the Proxy Write Timeout of 30 seconds cannot be adjusted.

If you regularly run HTTP requests that take over 100 seconds to complete (for example large data exports), move those processes behind a subdomain not proxied (grey clouded) in the Cloudflare DNS app.

Note

Please note that you may observe a 1 second difference between the timeout you’ve set and the actual time at which the Error 524 is returned. This is expected, it’s due to the current work on implementing Pingora, our new proxy ↗. As a workaround you can simply set the timeout to 1 second more (121 seconds instead of 120 seconds for example).
Pages: 1 [2]
View full version: Timeouts can\'t download