user only sees white pages and gets a 403 after gitlab CI actions
this is actually just an issue to save other poor souls from investing hours of debugging...
One of our users was reporting that he after login he only sees white pages on our self hosted gitlab. When impersonating the user as an admin, we were faced with the same issue (after click you only see a completely blank page). Web dev tools show that you're only getting 403 for no matter what...
turns out, the solution is in this old issue: gitlab-foss#48111 (moved) Sadly it's locked, otherwise i'd just have added my comment there.
The location of that setting in the admin area actually was changed: you can find it under Reporting / Spam and Anti-bot Protection
as of version 13.1.4. For us it was set to restricting each user to 10 different IPs in 12h, which apparently was exceeded by some CI and deployment jobs using runners on various machines. From what i can see this doesn't seem to honor the rack_attack whitelist settings and seem to be a completely independent feature.
It would've greatly helped our users and admins if there was an actual helpful message to the user, but from what i can see that was already suggested before, so i'm doing what i can to help make this google-able at least...