We are struggling to keep Codebreg.org available for unauthenticated users due to massive abuse of expensive endpoints.
Our current priority is keeping Codeberg.org responsive for authenticated users.
We are struggling to keep Codebreg.org available for unauthenticated users due to massive abuse of expensive endpoints.
Our current priority is keeping Codeberg.org responsive for authenticated users.
@codebergstatus i had a lot of issues when hosting forgejo as well, i managed to mitigate them with Anubis + rate limiting via nginx + fail2ban
i mean were still cranking like ~10 gb a day on average but better than like 150 or however much it was before idr :D probably important to note that the instance isnt huge, all repos put together are like 10 gb if not less
best of luck fighting them bots
Codebreg.org was so expensive, you had to park it?!
All the best fighting these bots. #hugops
@codebergstatus At the moment, this causes some "downstream" projects to fail, e.g. building librewolf-bin on AUR (ArchLinux) fails. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=librewolf-bin#n73
> fatal: unable to access 'https://codeberg.org/librewolf/source.git/': TLS connect error: error:0A000126:SSL routines::unexpected eof while reading
I think you have a great mission and I hope you'll find a solution! ❤️
@codebergstatus sorry for the stupid question guys. But why would you want an unauthenticated endpoint for a repo? 🫡🥰
I'm an authenticated user btw...