Hey,
Bitbucket pipelines worked fine until yesterday. My pipelines build started failing repeatedly.
I went to Pipelines - SSH keys, and tried to fetch my host again to get the fingerprint.
While checking the response in devTools, I found that I get an error 429: Too many requests.
Also, in the header I see this value: x-request-count:297, which was about half an hour ago 550.
This confuses me a bit, since I know the bitbucket limit is 500, so in the case of 297 request counts, everything should work fine.
In addition, The request count is daily, so waiting a day should have reset my count.
Lastly, I know for a fact that the request count of our "entire" team was lesser than 500 since it's currently only me using the account and I've ran the bitbucket build for around 20 MAX times that day.
How can I resolve this?
I'm still seeing this issue on Bitbucket Premium: https://github.com/npm/npm/issues/20816
Using npm install -g npm@latest and npm ci
Hi @thibmaek,
it looks like there has been a change in npm ratelimiting that is impacting us.
There is an open npm issue here: https://github.com/npm/registry/issues/334
You can also track our status page: https://status.bitbucket.org/incidents/dt7bxd954z0m
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @imri_barr,
We did in fact have an issue with the fetching SSH keys, this has been resolved by now (got resolved last week).
Sorry for the inconvenience!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.