Jitpack.io: peer not authenticated error when downloading with gradle 2.10

Created on 8 Feb 2016  Â·  18Comments  Â·  Source: jitpack/jitpack.io

When trying to get a jitpack hosted dependency via gradle, I receive this error:

      > Could not resolve com.github.MKergall.osmbonuspack:OSMBonusPack:v5.7.
         > Could not get resource 'https://jitpack.io/com/github/MKergall/osmbonuspack/OSMBonusPack/v5.7/OSMBonusPack-v5.7.pom'.
            > Could not GET 'https://jitpack.io/com/github/MKergall/osmbonuspack/OSMBonusPack/v5.7/OSMBonusPack-v5.7.pom'.
               > peer not authenticated

When adding the parameter -Djavax.net.debug=ssl:handshake to the gradle call, I get this more verbose description of the problem:

PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

This is on Debian sid and the reason might the that JitPack's SSL certificate coming from COMODO is maybe not trusted by its java installation. Please note that I have verified that my java trust store at /etc/ssl/certs/java/cacerts is not empty. I even rebuilt it running:

sudo /var/lib/dpkg/info/ca-certificates-java.postinst configure

However, wget and browsers validate the certificate just fine. So the error might actually _not_ be with JitPack. I am posting it here anyway since it directly affects your main feature.

Most helpful comment

Using Gradle 2.11 instead of 2.10 indeed solves this issue. Thanks for the idea!

All 18 comments

Hi @grote

Thank you so much for the detailed analysis! There used to this kind of issue with SNI SSL certificates but jitpack.io is no longer using that so its strange to see it.
What is your environment OS/JDK/Gradle and proxy if any? Tried to get your dependency with gradle and could get it.

I can get the dependency just fine with wget and the browser as well, just Java does not validate the certificate. I am using Debian Sid. Java is:

OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

I am using Gradle 2.10 and no proxy. The issue seems to also exist with "Arch Linux x86_64 and openjdk 7" as per #424.

Using Gradle 2.11 instead of 2.10 indeed solves this issue. Thanks for the idea!

Oh wow, this has been driving me crazy for the past week. Thanks @grote for saving me once again.

Thanks a lot @grote for the solution!

Having the same issue in Maven -- does anyone understand what the nature of the fix in Gradle was?

+1
thanks @grote!

I would like to say that I have the same issue with maven using 3.0.2 on ubuntu. This was fixed by updating to the latest version of maven.

@dtracers Thank you for the information!

Updating to gradle 2.11 also worked for me! :+1:

updating to 2.11 worked for me too , thanks a lot

Got this message building a project on PhoneGap Build. My project uses a Cordova plugin which I developed myself and use in other Cordova projects. The problem only raises in PhoneGap Build.

* What went wrong:
A problem occurred configuring root project 'project'.
> Could not resolve all dependencies for configuration ':_debugCompile'.
   > Could not resolve com.github.50ButtonsEach:fliclib-android:ec1cdc3fbe.
     Required by:
         :project:unspecified
      > Could not GET 'https://jitpack.io/com/github/50ButtonsEach/fliclib-android/ec1cdc3fbe/fliclib-android-ec1cdc3fbe.pom'.
         > peer not authenticated

The plugin that I am uisng in my app is Cordova-Flic:
https://github.com/jguix/Cordova-Flic

Hi @jguix

Which version of Gradle are you using? This issue should have been fixed in 2.10
#514

I'm trying to figure it out. I don't know because it is a cloud build
(PhoneGap Build), out of my control. I asked in their community forums and
I'm waiting for a response.
El 27 may. 2016 12:34 p. m., "JitPack.io" [email protected]
escribió:

Hi

Which version of Gradle are you using? This issue should have been fixed
in 2.10

514 https://github.com/jitpack/jitpack.io/issues/514

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jitpack/jitpack.io/issues/423#issuecomment-222114901,
or mute the thread
https://github.com/notifications/unsubscribe/AB0GGY-_BCPREeBwUQMgS3_SfDksEgxWks5qFsi_gaJpZM4HVzVc
.

thanks @grote.

change jcenter() to this:
jcenter { url "http://jcenter.bintray.com/" }

this works for me.

change jcenter() to this:
jcenter { url "http://jcenter.bintray.com/" }

this works for me.

Not much of a fix. You're just turning off SSL.

change jcenter() to this:
jcenter { url "http://jcenter.bintray.com/" }
this works for me.

Not much of a fix. You're just turning off SSL.

Yes, it's not the right solution.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

SilenceDut picture SilenceDut  Â·  4Comments

bsideup picture bsideup  Â·  4Comments

afollestad picture afollestad  Â·  5Comments

mannodermaus picture mannodermaus  Â·  3Comments

jtang-ml picture jtang-ml  Â·  4Comments