[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers-public] 502 bad gateway (from nginx) when https://
From: |
Bob Proulx |
Subject: |
Re: [Savannah-hackers-public] 502 bad gateway (from nginx) when https://git.savannah.gnu.org/cgit/ |
Date: |
Thu, 2 Jan 2025 07:30:28 -0700 |
Juha Pohjalainen wrote:
> noticed that https://git.savannah.gnu.org/cgit/ gives 502 error when
> navigated from page https://git.savannah.gnu.org/
Our git server is often under attack by abusive agents. The whole
entire world is now scraping every possible URL for AI training, or at
least seemingly so. And then there are just the normal script kiddie
abuse. And all of the rest. It sometimes overloads the system. The
cgit interface is a very resource heavy interface to provide for a
human web browsing experience to the git repositories.
On the top level https://git.savannah.gnu.org/ page some system
resource information is provided. If the system is getting beat upon
this will usually show a high cpu load average and a high level of
memory use for the system. This helps get a window to view into the
system and how it is doing.
The Savannah admins often work on fail2ban rules to block abuse from
the net in order to keep the system from being overloaded. But it is
a never ending task because people are the problem and people are very
clever about evading blocks and abusing the system. At this moment
that I am writing this things seem to be doing acceptably well.
> And this I noticed, when trying to pull one repo from git.
When doing git pull one should be using the more efficient git backend
rather than the piggy piggy piggy cgit backend. That would help
regardless of other things. The cgit interface for the projects lists
the git http backend URL for individual projects. That cgit provides
an interface that is compatible with git is a misfeature IMNHO when
used in practice because it allows this type of mismatch to creep in
accidentally.
For git protocols please use the more efficient git backend:
https://git.savannah.gnu.org/git/
Not the piggy piggy piggy cgit human interface:
https://git.savannah.gnu.org/cgit/
That will probably help with the reliability of the protocols.
Bob