peer not authenticated (no proxy)

[renaudcerrato]

After clearing my gradle cache, all of the sudden I got Error: Cause: peer not authenticated on both Gradle (command line) and Android Studio. Here's the truncated stacktrace. It only happens only on my JitPack's dependencies:

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not resolve com.github.renaudcerrato:FloatingSearchView:1.0.1.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.renaudcerrato:FloatingSearchView:1.0.1.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom'.
               > peer not authenticated
   > Could not resolve com.github.renaudcerrato:ToggleDrawable:1.0.2.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.renaudcerrato:ToggleDrawable:1.0.2.
         > Could not get resource 'https://jitpack.io/com/github/renaudcerrato/ToggleDrawable/1.0.2/ToggleDrawable-1.0.2.pom'.
            > Could not GET 'https://jitpack.io/com/github/renaudcerrato/ToggleDrawable/1.0.2/ToggleDrawable-1.0.2.pom'.
               > peer not authenticated
   > Could not resolve com.github.square.leakcanary:leakcanary-android:b8e444b351.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.square.leakcanary:leakcanary-android:b8e444b351.
         > Could not get resource 'https://jitpack.io/com/github/square/leakcanary/leakcanary-android/b8e444b351/leakcanary-android-b8e444b351.pom'.
            > Could not GET 'https://jitpack.io/com/github/square/leakcanary/leakcanary-android/b8e444b351/leakcanary-android-b8e444b351.pom'.
               > peer not authenticated

I already Googled for it a lot and I'm not behind a proxy, and the workaround to that known issue didn't solved it.

By commenting all my JitPack's dependencies, Gradle is'nt complaining anymore (though the build just fails of course).

The interesting thing is that using http instead of https, raise the same error (which is a non-sense):

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not resolve com.github.renaudcerrato:FloatingSearchView:1.0.1.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.renaudcerrato:FloatingSearchView:1.0.1.
         > Could not get resource 'http://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom'.
            > Could not GET 'http://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom'.
               > peer not authenticated
   > Could not resolve com.github.renaudcerrato:ToggleDrawable:1.0.2.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.renaudcerrato:ToggleDrawable:1.0.2.
         > Could not get resource 'http://jitpack.io/com/github/renaudcerrato/ToggleDrawable/1.0.2/ToggleDrawable-1.0.2.pom'.
            > Could not GET 'http://jitpack.io/com/github/renaudcerrato/ToggleDrawable/1.0.2/ToggleDrawable-1.0.2.pom'.
               > peer not authenticated
   > Could not resolve com.github.square.leakcanary:leakcanary-android:b8e444b351.
     Required by:
         ***:app:1.0.14
      > Could not resolve com.github.square.leakcanary:leakcanary-android:b8e444b351.
         > Could not get resource 'http://jitpack.io/com/github/square/leakcanary/leakcanary-android/b8e444b351/leakcanary-android-b8e444b351.pom'.
            > Could not GET 'http://jitpack.io/com/github/square/leakcanary/leakcanary-android/b8e444b351/leakcanary-android-b8e444b351.pom'.
               > peer not authenticated

Using curl (or my navigator) doesn't show any error:

renaud@stealth:~$ curl -L -v http://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom
*   Trying 104.24.22.62...
* Connected to jitpack.io (104.24.22.62) port 80 (#0)
> GET /com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom HTTP/1.1
> Host: jitpack.io
> User-Agent: curl/7.43.0
> Accept: */*
> 
< HTTP/1.1 301 Moved Permanently
< Date: Thu, 07 Apr 2016 22:52:55 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=de59ea407a17d14802a8293738ee35f1b1460069575; expires=Fri, 07-Apr-17 22:52:55 GMT; path=/; domain=.jitpack.io; HttpOnly
< Location: https://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom
< CF-Cache-Status: HIT
< Expires: Thu, 07 Apr 2016 23:22:55 GMT
< Cache-Control: public, max-age=1800
< Server: cloudflare-nginx
< CF-RAY: 29010d7d210b07b5-MIA
< 
* Ignoring the response-body
* Connection #0 to host jitpack.io left intact
* Issue another request to this URL: 'https://jitpack.io/com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom'
* Found bundle for host jitpack.io: 0x562ed3cc0dc0
*   Trying 104.24.23.62...
* Connected to jitpack.io (104.24.23.62) port 443 (#1)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* found 704 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_ECDSA_AES_128_GCM_SHA256
*        server certificate verification OK
*        server certificate status verification SKIPPED
*        common name: ssl387629.cloudflaressl.com (matched)
*        server certificate expiration date OK
*        server certificate activation date OK
*        certificate public key: EC
*        certificate version: #3
*        subject: OU=Domain Control Validated,OU=PositiveSSL Multi-Domain,CN=ssl387629.cloudflaressl.com
*        start date: Tue, 22 Mar 2016 00:00:00 GMT
*        expire date: Sun, 25 Sep 2016 23:59:59 GMT
*        issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO ECC Domain Validation Secure Server CA 2
*        compression: NULL
* ALPN, server accepted to use http/1.1
> GET /com/github/renaudcerrato/FloatingSearchView/1.0.1/FloatingSearchView-1.0.1.pom HTTP/1.1
> Host: jitpack.io
> User-Agent: curl/7.43.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Server: cloudflare-nginx
< Date: Thu, 07 Apr 2016 22:52:55 GMT
< Content-Type: text/xml
< Content-Length: 1069
< Connection: keep-alive
< Set-Cookie: __cfduid=d14749fd8399279df197c4ddd7b8743e21460069575; expires=Fri, 07-Apr-17 22:52:55 GMT; path=/; domain=.jitpack.io; HttpOnly
< ETag: 69c7b95c0ab4c085b0650db870bdc62a38294d64
< Cache-Control: public, max-age=86400
< Last-Modified: Mon, 01 Feb 2016 19:55:30 GMT
< CF-Cache-Status: HIT
< Expires: Fri, 08 Apr 2016 22:52:55 GMT
< CF-RAY: 29010d7eedb30358-MIA
< 
<?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>com.github.renaudcerrato</groupId>
  <artifactId>FloatingSearchView</artifactId>
  <version>1.0.1</version>
  <packaging>aar</packaging>
  <developers>
    <developer>
      <name></name>
      <email></email>
    </developer>
  </developers>
  <scm>
    <connection>scm:null</connection>
    <developerConnection>scm:null</developerConnection>
  </scm>
  <dependencies>
    <dependency>
      <groupId>com.android.support</groupId>
      <artifactId>recyclerview-v7</artifactId>
      <version>23.1.1</version>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>com.android.support</groupId>
      <artifactId>appcompat-v7</artifactId>
      <version>23.1.1</version>
      <scope>compile</scope>
    </dependency>
  </dependencies>
</project>

Any clue?

[jitpack-io]

Hi

There was a bug in HttpClient library used by Gradle which caused this issue.
It was fixed in Gradle 2.11 so upgrading should fix it.

[renaudcerrato]

Hi there!

I forgot to mention I'm using Gradle 2.4:

renaud@stealth:~/Workspace/project$ ./gradlew --version
------------------------------------------------------------
Gradle 2.4
------------------------------------------------------------

[jitpack-io]

@renaudcerrato Any chance you could upgrade to Gradle 2.12?

[renaudcerrato]

2.12 doesn't seem to be an upgrade:

A problem occurred evaluating project ':app'.
> Failed to apply plugin [id 'com.android.application']
   > Gradle version 2.2 is required. Current version is 2.12. If using the gradle wrapper, try editing the distributionUrl in /home/renaud/Workspace/popsy/gradle/wrapper/gradle-wrapper.properties to gradle-2.2-all.zip

Same issue with 2.2. My workstation is completely stucked - on JitPack dependencies.

[jitpack-io]

Ah yes, if you upgrade to newer Gradle then the android plugin needs to be upgraded as well
classpath 'com.android.tools.build:gradle:2.0.0'

[renaudcerrato]

Indeed, using Gradle 2.12 on Android Gradle plugin 2.0.0 did the trick. Thanks! ᐧ