Timeouts can't download
Are they working on fixing the download timeouts or is it just me?Coins are taken quickly no problem :)
Viewing pages are fast no problem :)
ONLY waiting for downloads time out:(
Seems magazines and books are especially hard to download getting cloudflare time out error page.
pindiy.com Host Error
If you're the owner of this website: The connection to the origin web server was made, but the origin web server timed out before responding. The likely cause is an overloaded background task, database or application, stressing the resources on your web server. To resolve, please work with your hosting provider or web development team to free up resources for your database or overloaded application.
Patterns seem to eventually show up to download but the file name is a date not file name.
I've tried refreshing after spending coins - no difference still times out.
iBooks times out as well.
I have had downloads take several seconds (up to 15-20 seconds) to work, but I have never had the timeout issue that you describe. 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). This issue STILL continues with cloudflare errors
Numerous tries with this file today:
www.pindiy.com/thread-637576-1-1.html
gives this cloudflare error:
If you're the owner of this website:
The connection to the origin web server was made, but the origin web server timed out before responding. The likely cause is an overloaded background task, database or application, stressing the resources on your web server. To resolve, please work with your hosting provider or web development team to free up resources for your database or overloaded application
Very frustrating when you have to go make a coffee then come back hoping the download pops up!
Mostly with larger files like books or magazines although regular patterns are still very slow to pop up the download link.
Rest of site if fast no issues I've been having slow downloads as well. Sometimes the file downloads with the correct name, sometimes with just a date as you've mentioned.
I've also noticed that if I do not refresh the page after purchasing, the download never works, I've had that problem since the very first file I tried to download.
I have never gotten the cloudflare page though. Update...
Haven't been getting time out cloudflare page but still EXTREMELY slow for the download to show up and it's always a date not file name Same issue here with a cross stitch book.Tried 2 different browsers but download just timeouts.Please advise! 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 Downloads are also very slow for me, but they end up working.
@Turquoise can you please help? I can see her issue being accurate I'm also having this issue with some of the downloads. Sometimes refreshing works, other times it just keeps timing out.
I'm having the same time out issue as poster... same msg. Been trying to download the same book for over an hour to no avail. I thought it was just me! Thanks for asking.
Pages:
[1]
2