Received fatal alert: protocol_version or peer not authenticated from Maven Central Solved

(761 Views)


In June 2018, in an effort to raise security and comply with the modern standards, Maven Central and Bintray have announced that the insecure TLS 1.0 & 1.1 protocols will no longer be supported for SSL connections to Central. According to the estimations, this should only affect users of Java 6 or 7 and using Gradle versions 2.1 through 4.8 who are also using https to access central,which by our metrics is less than 0.2% of users. This is the reason behind facing this error.

For Java 7 users, there is a workaround.Try to enable TLS 1.2 protocol with Java property in the command line and see if this resolves the issue.

mvn -Dhttps.protocols=TLSv1.2 install
Here, install is an example of a goal.

You should take action if the following are applicable in your case:

  • JVM version is Java 7u130 or lower than that.
  • The gradle version is between 2.1 and 4.8, both inclusive.
  • You have declared a repository {} of mavenCentral() or jcenter().

You can take any of the following steps to use TLS v1.2+:

  • Run Gradle with Java 1.7.0_131-b31 or above.
  • Upgrade to Gradle 4.8.1 or above.
  • Replace mavenCentral() with maven { url = "http://repo.maven.apache.org/maven2" } and jcenter() with maven { url = "http://jcenter.bintray.com" }

As the third opens a possible attack vector,the first two solutions are recommended as a solution.

Solution Worked 4 UpvotesUpvote

        

Solution Didn't Worked 0 DownvotesDownvote



Comments



Search




Search Tags