#32 "504 Gateway Time-out" following every attempt to upload through the web interface

I'm attempting to update a couple very small (<30 KB) text files in a private repository by uploading the new versions through the web interface, one at a time (one file per commit). After pressing "Commit Changes", my browser waits for a response from the server for about a minute before displaying this:

504 Gateway Time-out

The server didn't respond in time.

I've tried this half a dozen times with the same response each time, though the first time I attempted this it actually succeeded in creating the commit despite the message.

I also tried uploading a new test file, rather than updating an existing file, with the same result.

EDIT: The first couple of my several failed commit attempts just appeared in the commit history with timestamps several minutes later than when they were really committed. I guess everything is just slow? I'm hoping the others come through soon too.

Thanks for bringing it to my attention. I'm seeing it too. Looking into it now.

After waiting 20+ minutes, all of my commits have finally come through.

That's good to know. It seems the commit in the backend is taking too long and reaches the timeout of the frontend. Still digging.

Thanks for looking into this @achilleas!

Small update on this issue.

I've found a couple of (potential) root causes and I'm testing their impact now. I'll expect I'll be deploying updates within the next few days.

Thanks again for your continued effort on this @achilleas! GIN is a great service thanks to your (and I assume also others') hard work!

Hi again Jeffrey,

I've updated the server and some relevant configuration options. Commits should be faster now when uploading. One issue with the previous setup was that regardless of the size and number of the new files being uploaded, if there were many files in the existing repository, especially many large files, the commit would be very slow.

The commits should generally be faster now and they should also be unaffected by the size and number of files already in the repository.

In addition, the server should be a bit less eager time out. So even when committing big changes that can take a while, you shouldn't be seeing 504 errors.

Can you try making some changes to the same repository, or one of a similar size, and confirm the issue is resolved?

I'm closing this issue and assuming it's resolved. If it happens again, please feel free to open a new one.