New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Origin Connection Time-out #3973
Comments
Same problem for me, different project. Not knowing why the timeout since I can lookup the repo and the files are there. Netbeans 8.2 patch 2 |
Hi @ligi, Indeed, it should be a 404 and we've made some changes. |
now I am also getting a 404 and the error is no more. Might be just a fluke - feel free to close. But also feel free to open to track down if this repeats (e.g. under certain server loads) as it seems I was not the only one with the problem.
|
We're also having this problem for a different dependency. |
I'm having problems since 2 days ago similar to this, with other dependencies:
Are there any solutions for this ? |
We are having a similar issue with pulling the maven-metadata.xml file for braintree. We can no longer build our project due to the issue.
|
Same for me:
|
Same here, for multiple public projects like Glide and Coil. Also our own private repos. Not good. |
Same here. I haven't been able to build my Android app because of this 522 timeout problem. |
I've found a workaround: |
Worked, great catch. |
Can confirm, workaround is good. @appach22 , Thank you. |
Confirming; workaround seems to work, original problem has been persisting at least over the weekend (leading to intermittent build failures - not clearly repeatable which dependencies are hit). |
@jitpack-io I'm unable to build my project due to this issue. My build.gradle is https://github.com/Gamebuster19901/ONIs-Arsenal/blob/1.14.4/build.gradle And the error I'm getting is:
Additonally the workaround presented by appach22 does not work, and results in the following:
|
Having the same issue. My breaks like this.
|
@wdtaylor strange, I'm getting a 404 for https://jitpack.io/com/zendesk/support/2.2.1/support-2.2.1.jar that instead of a 522 |
@Gamebuster19901 zendesk is actually hosted here. maven { url 'https://zendesk.jfrog.io/zendesk/repo' } |
I can verify that adding www. worked to resolve the issue. |
Huge thanks to @appach22 for finding the workaround. Bug is still there, workaround works for me. I have made my todo item "Remove dependency on JitPack" rise up to the top of my list. I am amazed that after one week, JitPack has neither solved this issue, nor even given a word of reply, while this problem would prevent anybody from getting any work into production without the workaround. The JitPack home page instructions have not even been updated with the workaround, still mentioning only |
I agree with @vic-cw. There's no way @jitpack-io hasn't noticed this. It'd be great if they could shed some light regarding the problem, the solution, and the temporal workaround. |
I'm assuming jitpack is using cloudflare. Perhaps they need to take a look at https://support.cloudflare.com/hc/en-us/articles/115003011431#522error |
This definitely seems to still be an issue. I cleared my Gradle caches today and all of a sudden I could not get any of my jitpack dependencies. I was seeing the 522's in my gradle logs with The workaround thankfully seems to have worked for me. |
My workaround was to make sure Jitpack is last in the repository list. Jitpack's documentation does say:
|
I reached out on twitter to jitpack about this issue and they answered that they will look into it: |
Seems jitpack is trying out a fix: https://twitter.com/jitpack/status/1193853023862378496 anyone still experiencing the issue? |
Yes; we're still seeing this issue in Azure pipelines builds |
Put maven { url "https://jitpack.io" } to repositories under |
I cannot believe this actually works 😱 |
but why? |
why |
2021 and issue is still popping up |
Yes it is |
2021 and issue is still popping up |
Worked😀 repositories { |
I am also facing the error. Although added error:- |
Literally happens all the time now. I fix it with one library that used to depend on Jitpack and now it just moves onto another one. Seems to fail my builds about 40% of the time over just this one issue. Seems to me like Jitpack is giving up the ghost. |
@oliverspryn same here :( any updates? |
Looks like removing the - maven { url 'https://www.jitpack.io' }
+ maven { url 'https://jitpack.io' } |
This issue is stale because it has been open for 30 days with no activity. |
Uninstall Android Studio fullly and reinstall |
hi i am also having same issue.....but i am on expo eas setup....i won't have build.gradle file....what should i do to make it work? |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Yep @berchoes . I've pretty much left Jitpack altogether. I use Maven Central for all dependencies that I can, and if I need a library that is only hosted on Jitpack, I proxy it through Artifactory. That way, my dependencies always come via Artifactory and it is a much more reliable mirror. |
problem happening today Jitpack.io off build.gradle(Project) build.gradle(Module) settings.gradle(Project) Problem |
I am currently having builds fail like this:
these artifacts should not come via jitpack - and IMHO jitpack should return a 404 there
The text was updated successfully, but these errors were encountered: