On Sun, May 4, 2025 at 8:24 AM Bastien Guerry <b...@gnu.org> wrote: > > Corwin Brust <cor...@bru.st> writes: > > > If you will each raise a support ticket including the public IP(s) you > > are using connecting to Savannah we can at least unblock then and > > probably get them added to an allow/ban-exclude list. > > Mhh... I'm still getting random 502 errors when trying to clone from my > machine (146.185.138.54 / 2a03:b0c0:0:1010::270:200) > > From where can I "raise a support ticket"? >
You can raise a support ticket here: https://savannah.nongnu.org/support/?group=administration&func=additem And we should probably do that to unblock any IPs you use personally, but.... Considering that your use-case is CI/build-runners perhaps you would like to test drive the new read-only mirrors system that Bob has been designing.. You should simply be able to clone your project using the new DNS name: https://https.git.savannah.gnu.org/git/<...rest of the path to clone your project..> This has been created expressly to offload the "extra" overhead on Savannah's side that is involved with adding the HTTPS protocol atop the underlying SSH based access to the git service for users doing anonymous clones of git repositories. Initial reports suggest this is working. Given things continue as such I expect we'll both increase the number of services that have a read-only mirror like this and also we might eventually retire direct access to Savannah for making read-only copies. But those decisions have not been made. Right now we are looking for evidence this works well for people
