504 Gateway Time-out #1

Open
opened 6 years ago by jebba · 3 comments
jebba commented 6 years ago
Owner

When doing a New Migration, mirroring this repo:

https://code.alephobjects.com/source/aof/

I got this error:

504 Gateway Time-out
nginx/1.10.3

The repo was created OK.

When doing a New Migration, mirroring this repo: https://code.alephobjects.com/source/aof/ I got this error: 504 Gateway Time-out nginx/1.10.3 The repo was created OK.
jebba commented 6 years ago
Poster
Owner

Again, when mirroring animas.

https://code.alephobjects.com/diffusion/ANI/

The repo was not created ok.

Again, when mirroring animas. https://code.alephobjects.com/diffusion/ANI/ The repo was not created ok.
jebba commented 6 years ago
Poster
Owner

Second time mirroring animas had Gateway timeout.

The repo was created, but it fails when you go there:

https://code.forksand.com/AlephObjects/ANI

It displays a big "500" and nothing else except the gitea template.

Edit: Looks like Gitea automatically cleaned up and removed the repo.

Second time mirroring animas had Gateway timeout. The repo was created, but it fails when you go there: https://code.forksand.com/AlephObjects/ANI It displays a big "500" and nothing else except the gitea template. Edit: Looks like Gitea automatically cleaned up and removed the repo.
jebba commented 6 years ago
Poster
Owner

I've done 100+ git repo mirrors now, and have seen this timeout often. It happens if it is mirroring a large repo. Usually, unless there is a problem with the server on the other side (e.g. Phabricator with large https) the repo will eventually mirror. It would be nice if it just said "come back to see your repo mirrored" instead of an nginx timeout.

I've done 100+ git repo mirrors now, and have seen this timeout often. It happens if it is mirroring a large repo. Usually, unless there is a problem with the server on the other side (e.g. Phabricator with large https) the repo will eventually mirror. It would be nice if it just said "come back to see your repo mirrored" instead of an nginx timeout.
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Reference: forksand/code#1
Loading…
There is no content yet.