Gitlab.com returns 403 Forbidden


#1

Hello All,
I have been using gitlab.com for a while now BUT just recentlyI found that i am unable to connect to the https://gitlab.com site. When i try to connect, i get “403 forbidden” returned.
If i plug my pc into another network, it works. It would appear that our public ip address has been banned.
Does anyone know how to fix this issue.
Is there anyone i can contact to get our ip address un-banned?
Thanks
Stuart


#2

bump,
sorry, I still haven’t found a solution to this yet


#3

Im having the same issue since today, did you ever get ever get around it, or did it just start working again after a while ?
Accessing gitlab through my mobile provider still works, but through my home network alI get is ‘Forbidden’ at each request.

edit: Nevermind, just got access again shortly after posting this…


#4

Im having the same issue since today. ¿Why does this happen?. I can’t access gitlab.com from my company’s network.


#5

we experienced the same issue today with a locally running GitLab instance from the official Docker image (with little adaptations to make it work in our proxied environment) - seemingly out of nowhere - and had to restore from a backup.
Nothing suspicious in the nginx logs, and we were not IP blocked by the rack attack config (checked with mobile access and it also didn’t work).


#6

Just got this now, can access from phone and ssh, but not HTTP on the wifi or lan. Seems like a temporary IP block to me. Of course mine hasn’t lifted yet. I use Gitlab all the time… maybe I hit some sort of requests/day limit?

Not sure what’s up here.

=== Addendum ===

Could this be runner related?


#7

Same here. Did you solve this?