Why am I getting Received fatal alert protocol version or peer not authenticated from Maven Central

Question

I m getting the below errors when connecting to Maven Central   https   repo1 maven org after June 18th 2018   Received fatal alert  protocol version   or  Received fatal alert  peer not authenticated

User · Answer

Solution 1  configure Java 7   It is need to enable TLS 1 2 protocol with Java property in the command line  mvn -Dhttps protocols TLSv1 2 install   install is just an example of a goal  The same error for ant can be solved by this way  java -Dhttps protocols TLSv1 2 -cp  ANT HOME  lib ant-launcher jar org apache tools ant launch Launcher   Solution 2  use Java 7 with Oracle Advanced Support  Also problem can be solved by updating the Java 7 version  But the last available version  7u80  doesn t fix the problem  It is need to use an update provided with Oracle Advanced Support  formerly known as Java for Business    Solution 3  use Java 8 instead   Configure  JAVA HOME to point to Java 8

User · Answer

As said  v ladynev  it works with JDK 1 7  With Eclipse  to be able to perform a  Run As  maven install with the TLS command-line parameter  just configure the JDK you re using   Open the dialog through Window   Preferences   Java   Installed JREs   Then highlight the one you re using  should be a JDK  not a JRE   click on Edit  In the field  Default VM arguments   fill the value -Dhttps protocols TLSv1 TLSv1 1 TLSv1 2  As shown below     Clean the project  maybe optional   then re-run a maven install

User · Answer

For setting java properties on Windows app server    configure tomcat   run as admin then add Java opts  restart service

User · Answer

I m sorry  I don t know why you get the error message  However  I m using Java 7 and Windows 10 and the solution for me was to temporarily use Java 8 by changing the JAVA HOME environment variable  Then I could run mvn install and fetch from Maven Central Repository

User · Answer

Using jdk7-u221  I was need to install the Java Cryptography Extension  JCE  Java Cryptography Extension JCE

User · Answer

The following command helped me  executing on bash before running mvn   export MAVEN OPTS -Dhttps protocols TLSv1 TLSv1 1 TLSv1 2

User · Answer

In June 2018  in an effort to raise security and comply with modern standards  the insecure TLS 1 0  amp  1 1 protocols will no longer be supported for SSL connections to Central  This should only affect users of Java 6  and Java 7  that are also using https to access central  which by our metrics is less than  2  of users   For more details and workarounds  see the blog and faq here  https   blog sonatype com enhancing-ssl-security-and-http 2-support-for-central

User · Answer

Update maven version to 3 6 3 and run mvn -Dhttps protocols TLSv1 2 install  it worked on centos 6 9

User · Answer

Note that if you re using the IBM JDK you may also have to set   com ibm jsse2 overrideDefaultTLS true  https   www ibm com support knowledgecenter SSYKE2 8 0 0 com ibm java security component 80 doc security-component jsse2Docs matchsslcontext tls html matchsslcontext tls

[maven] Why am I getting "Received fatal alert: protocol_version" or "peer not authenticated" from Maven Central?

Examples related to maven

Examples related to maven-central