XiphInfra:GitLab VM: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
== AI Scraper Blocking (Anubis) == | |||
To help with the recent flood of AI scrapers on the Xiph GitLab instance, which made it return 50x errors | |||
most of the time due to being hopelessly overloaded, Anubis was deployed which tries to identify these | |||
and presents a challenge for them to solve or blocks them outright. | |||
If you encounter issues due to this as legitimate user, please contact ePirat on IRC. | |||
== IP blocks == | == IP blocks == | ||
We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance. | We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance. | ||
Latest revision as of 15:00, 27 September 2025
AI Scraper Blocking (Anubis)
To help with the recent flood of AI scrapers on the Xiph GitLab instance, which made it return 50x errors most of the time due to being hopelessly overloaded, Anubis was deployed which tries to identify these and presents a challenge for them to solve or blocks them outright.
If you encounter issues due to this as legitimate user, please contact ePirat on IRC.
IP blocks
We have a number of IP ranges blocked to prevent huge amounts of spam to the GitLab instance.
The IP blocks are configured in /etc/gitlab/gitlab.rb in the nginx['custom_gitlab_server_config'] option. Additionally there is a custom error page for when the IP is blocked, which is stored at /var/www/html/gitlab-ipblock.html.
After making changes to the gitlab.rb, you need to run sudo gitlab-ctl reconfigure for the changes to be applied to the actual config files. Under no circumstances edit the generated config files directly, always use the gitlab.rb config.
In case you made an error in the configuration and something is not working as expected or some components, for example nginx, are not starting anymore, you can use sudo gitlab-ctl tail to view logs.