CI Runners Suddenly Failing with 403 Forbidden for Maven/Gradle Repositories (ubuntu-latest) #183607
-
Why are you starting this discussion?Bug What GitHub Actions topic or product is this about?Actions Runner Discussion DetailsSince today, our CI pipelines running on ubuntu-latest and other hosted runners have started failing while downloading dependencies from Maven/Gradle repositories, returning HTTP 403 Forbidden errors. Observed Behavior : Maven/Gradle dependency resolution fails with 403 Forbidden anybody facing same issue? |
Beta Was this translation helpful? Give feedback.
Replies: 49 comments 37 replies
-
Update @ Jan 06 16:13 UTCIssue is resolved on Maven Central https://github.com/orgs/community/discussions/183607#discussioncomment-15425901 Update @ Jan 06 15:32 UTC
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Similar issue. Task :gradle-plugin:react-native-gradle-plugin:jar |
Beta Was this translation helpful? Give feedback.
-
|
Same here https://github.com/quarkiverse/quarkus-cxf/actions/runs/20747407259/job/59567930499#step:4:1642 |
Beta Was this translation helpful? Give feedback.
-
|
It started this morning at around Tue, 06 Jan 2026 10:00:00 GMT; dependency resolution fails with "Received status code 403 from server: Forbidden" when trying to download from repo.maven.apache.org. |
Beta Was this translation helpful? Give feedback.
-
|
same problem |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure that makes a difference? (Locally I can build just fine, the 403's are only there on the GitHub Actions runners.) |
Beta Was this translation helpful? Give feedback.
-
|
Local runs work fine without changes, but this was a must for GitHub Actions. |
Beta Was this translation helpful? Give feedback.
-
|
I fail to see how it could solve things, since your error was:
and all your config changes is point central to https://repo.maven.apache.org/maven2, which would make zero difference AFAICT. |
Beta Was this translation helpful? Give feedback.
-
|
Retrying the run sometimes runs successfully, but it is really annoying! |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/orgs/community/discussions/183607#discussioncomment-15425386 |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issues since this morning 403 forbidden |
Beta Was this translation helpful? Give feedback.
-
|
Here also we started receiving 403 Forbidden without any changes to actions. Does anyone has any update on what the issue is and what needs to be done for resolution? |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. Started a couple of hours ago. |
Beta Was this translation helpful? Give feedback.
-
|
Yes. The meme came true. I am yelling at cloud |
Beta Was this translation helpful? Give feedback.
-
|
same :( |
Beta Was this translation helpful? Give feedback.
-
|
same :( |
Beta Was this translation helpful? Give feedback.
-
|
Possible Causes: Solutions I recommend: Next Steps: Try Different Runner OS: Test if the issue affects windows-latest or macos-latest differently Verify Locally: Check if you can access the repositories directly from your location Report to GitHub: If this persists, report via GitHub Support |
Beta Was this translation helpful? Give feedback.
-
|
thanks |
Beta Was this translation helpful? Give feedback.
-
|
AI slop |
Beta Was this translation helpful? Give feedback.
-
|
what is the mirror you suggest that is safe? |
Beta Was this translation helpful? Give feedback.
-
|
Many androidx presubmit runs failed due to this. |
Beta Was this translation helpful? Give feedback.
-
|
I have same issue in last a few hours. I was adding and reveritng some workarounds. Hard to say is fixed or I am just lucky :) |
Beta Was this translation helpful? Give feedback.
-
I can confirm it was just luck as after pullRQ merged master post commit check failed same... |
Beta Was this translation helpful? Give feedback.
-
|
Unhelpfully generic (and quite possibly AI-generated) comments aside 🫤 , most of my builds are starting to pass again now, the only exception being the CodeQL actions which are still consistently failing with 403's (in the Autobuild step). Let's hope everything shortly becomes stable again. 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
Having the same issue here, but it is not "resolving itself" for us at the moment. |
Beta Was this translation helpful? Give feedback.
-
|
same here 🤭 |
Beta Was this translation helpful? Give feedback.
-
|
also happens to me |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
Another one going crazy here since 11am CET... |
Beta Was this translation helpful? Give feedback.
-
|
We also have sporadic failures in our builds for projects that use Maven Central. We have other builds that use maven central by proxy over AWS codeartifact that are fine. |
Beta Was this translation helpful? Give feedback.
-
|
Tagging in here! |
Beta Was this translation helpful? Give feedback.
-
|
Two things:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm also seeing this issue |
Beta Was this translation helpful? Give feedback.
-
|
Please, if you have no further details to add, use the upvote and subscribe buttons instead of leaving "me too" comments. |
Beta Was this translation helpful? Give feedback.
-
|
It's up to maven central to let us build again apparently |
Beta Was this translation helpful? Give feedback.
-
|
403s being returned from CloudFlare when accessing repo.maven.apache.org/repo1.maven.org |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/orgs/community/discussions/183607#discussioncomment-15425386 |
Beta Was this translation helpful? Give feedback.
-
|
The issue seems to be gone. Can anyone also confirm? |
Beta Was this translation helpful? Give feedback.
-
|
No, the incident is still open: https://status.maven.org/incidents/n7h6lz2sy5gw |
Beta Was this translation helpful? Give feedback.
-
|
@kagahd Brian Fox posted earlier that the incident had to be created manually, so might need to be resolved manually (i.e., with a bit of a delay) too. FWIW, I can confirm our builds are working again. |
Beta Was this translation helpful? Give feedback.
-
|
@nscuro, since Brian Fox wrote that's IP based, maybe some IP's are still blocked. |
Beta Was this translation helpful? Give feedback.
-
|
We left this up while we waited for better correlation that it's resolved. |
Beta Was this translation helpful? Give feedback.
-
|
Finally this issue got fixed 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I think "finally" might be a little harsh. My take is that:
|
Beta Was this translation helpful? Give feedback.
-
|
I know this has been answered at the time, but some ecosystems started seeing 429s from Maven last week again (e.g. see https://clojurians.slack.com/archives/C0AB48493/p1778381725840669), which is likely related to newly introduced limits explained on https://central.sonatype.org/faq/429-error/. I wonder if Github would be in a position to establish some kind of peering connection with Sonatype to ensure customers are not disrupted? https://central.sonatype.org/faq/429-infrastructure-provider/#why-we-need-to-talk-directly |
Beta Was this translation helpful? Give feedback.
Brian Fox from Sonatype / Central here. We have started an outage incident to resolve this. Early indications are that something triggered the CDN DDOS algorithm and that's what is causing the 403s, but we are still investigating.