Question

Often gateway timeouts (504) from Spaces

Anyone also have this? And when will this be solved?

Subscribe
Share

Same here.

We just spent a lot of effort moving our systems to spaces… and now it completely chokes?

When I asked about limits during the trial they told me spaces could handle 200 requests per second… I’m lucky if I can get five requests working per minute.

Frustratingly yes.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Same here, have been getting timeouts for the last 3 weeks almost every day, this is a serious concern.

Waiting for a reply to our ticket.

We had the same problem with the CDN of DO. We still use spaces for hosting files but we put another CDN in front of spaces.

I ran a script to make 100 different requests to a DigitalOcean Spaces in SGP1 region, both through CDN and directly to origin. Here is the result I found:

  • Without CDN, all requests seem to work fine.
  • With CDN, “HTTP/1.1 504 Gateway Timeout” is returned up to 17% (!!!) of the time.

The responses from CDN includes the X-HW header, which from Googling points to StackPath CDN. So, it seems like either the CDN connectivity to DigitalOcean Spaces or StackPath itself (or both) is currently seriously broken.

Sorry to drag up an old post. I recently move my systems to digital ocean spaces, I am moving large(ish) files upto 20mb maybe one per second (max), and I get 504 a few times a day. Any further notice on this? Never had this issue on S3…

Yes, frequently. They told me in a ticket that they are working to make it more reliable.