SSLHandshakeException - Chain chain validation failed, how to solve?

Question

in my application I am trying to do a HTTPS POST request to my server. However, I keep getting SSLHandshakeException - Chain chain validation failed, all the time. I tried to send a request using POSTMAN and I got a response from the server. What can be causing this error when I try to send the request from the application?

Here a code snippet where I try to send the post request:

   public static JSONObject getDataLibConfiguration(Context context) throws HttpRequestException {

    int statusCode = 0;

    JSONObject commonInformation;
    HttpsURLConnection connection = null;

    try {

        commonInformation = ConfigurationProcessor.getCommonInformation(context);
        if (commonInformation == null) {
            return null;
        }

        URL url = new URL(BuildConfig.SERVER_CONFIG_URL);
        if (BuildConfig.DEBUG) {
            LogUtils.d(TAG, "url = " + url.getPath());
        }

        connection = getHttpsConnection(url);
        connection.setDoOutput(true);
        connection.setDoInput(true);
        connection.setRequestMethod("POST");
        connection.setRequestProperty("Content-Type", "application/json; charset=UTF-8");
        connection.setRequestProperty("Content-Encoding", "gzip");

        byte[] gzipped = HttpUtils.gzip(commonInformation.toString());
        cos = new CountingOutputStream(connection.getOutputStream()); //<-- This is where I get the exception
        cos.write(gzipped);
        cos.flush();

        statusCode = connection.getResponseCode();
        // More code her
 }

private static HttpsURLConnection getHttpsConnection(URL url) throws IOException, GeneralSecurityException {

        HttpsURLConnection connection = (HttpsURLConnection) url.openConnection();

        try {
            SSLContext sslContext = SSLContext.getInstance("TLS");
            MatchDomainTrustManager myTrustManager = new MatchDomainTrustManager(url.getHost());
            TrustManager[] tms = new TrustManager[]{myTrustManager};
            sslContext.init(null, tms, null);
            SSLSocketFactory sslSocketFactory = sslContext.getSocketFactory();
            connection.setSSLSocketFactory(sslSocketFactory);
        } catch (AssertionError ex) {
            if (BuildConfig.DEBUG) {
                LogFileUtils.e(TAG, "Exception in getHttpsConnection: " + ex.getMessage());
            }
            LogUtils.e(TAG, "Exception: " + ex.toString());
        }
        return connection;
    }

It just says: "java.security.cert.CertificateException: Chain validation failed" — Keselme, Nov 12 '18 at 16:58

Vadim · Answer 1 · 2023-06-15T12:35:00.887

207

In my case it was wrong date on the phone.

Fixing the date resolved an issue

edited Jun 15 '23 at 12:35

answered Aug 01 '19 at 08:05

Vadim

3,855
2
17
22

1

I got the same issue with an android tv emulator. Updating the date and setting the right time zone solved the problem. – Loïc Dumas Mar 16 '21 at 14:49
1

This was the solution for me. I just set date to "automatic" and it worked. But is there a way to make it work with "manual" date settings? – Krishnom May 12 '21 at 01:42
1

@Krishnom, should work if you manually set right time – Vadim May 17 '21 at 06:07
3

The reason of problem on Android 12 emulator was the same. Cold boot of emulator worked for me. – Eugene Babich May 10 '22 at 06:55
13/09/2022 - I noticed that every time I start the same emulator, its date is always set to the day before, make sure to verify this. – Pedro Massango Sep 13 '22 at 10:48
I also had this same issue for a number of phones and realised that the date was off on all of them. Changing it to automatic fixed the issue. – John Spax May 15 '23 at 12:22

score 45 · Answer 2 · answered Aug 28 '20 at 07:45

45

If you're using an emulated device it may solve the problem if you just 'Cold Boot' it.

Sometimes the date on those things can get stuck if you let them run for some time, which results in this expired-certificate-problem.

answered Aug 28 '20 at 07:45

Sebastian Müller

451
4
4

score 33 · Accepted Answer · answered Nov 14 '18 at 10:11

33

The problem was that the certificate was expired.

answered Nov 14 '18 at 10:11

Keselme

3,779
7
36
68

but in my case, It is working on almost all devices but few are getting this error message – Amin Pinjari May 17 '19 at 10:37
which certificate? how to renew? – ahmadalibaloch Aug 04 '20 at 07:37
1

@ahmadalibaloch The server I was sending the request to had a certificate that was expired so I had to renew it on GoDaddy. – Keselme Aug 04 '20 at 11:01
4

In my case, my emulator date not updated. It was few weeks late – Abdulmoiz Esmail Aug 28 '20 at 00:48
1

this was my first guess, but no, it was the wrong date time. It is odd that it happens for that reason. – WilliamX Sep 30 '22 at 02:15
In my case, the certificate was expired. In the logcat got 'javax.net.ssl.SSLHandshakeException: Chain validation failed' or 'Caused by: java.security.cert.CertificateExpiredException: Certificate expired at...' – Waseem Feb 17 '23 at 11:38

score 32 · Answer 4 · answered Nov 10 '21 at 09:48

32

In my case, I fetch this issue on Android Emulator. When I clear emulator cache has resolved the issue.

answered Nov 10 '21 at 09:48

Md Imran Choudhury

9,343
4
62
60

1

This worked for me too, thank you for posting your solution, and thanks for google for giving such an amazing waste of time error description – MBH Feb 23 '23 at 14:23

score 14 · Answer 5 · answered May 21 '22 at 09:53

14

In my case, the issue was with the phone date. So please check it, set to automatic.

answered May 21 '22 at 09:53

Hayk Mkrtchyan

2,835
3
19
61

score 13 · Answer 6 · answered Feb 15 '21 at 21:03

13

My date and time were correct, but I didn't have "Use Network Provided Time checked" in my system settings.

I fixed this issue by going to Settings > Date and Time > Check "Use network-provided time" and also check "Use network-provided time zone".

Then this error went away.

answered Feb 15 '21 at 21:03

zetatlas

320
2
8

On a OnePlus 8, both are checked but the error occurs anyway. – 3c71 Mar 29 '21 at 07:41
solution works on android emulator – Rahul Mandaliya Dec 31 '21 at 07:45

score 10 · Answer 7 · answered May 24 '19 at 12:30

public static void trustEveryone() {
        try {
            HttpsURLConnection.setDefaultHostnameVerifier(new HostnameVerifier(){
                public boolean verify(String hostname, SSLSession session) {
                    return true;
                }});
            SSLContext context = SSLContext.getInstance("TLS");
            context.init(null, new X509TrustManager[]{new X509TrustManager(){
                public void checkClientTrusted(X509Certificate[] chain,
                                               String authType) throws CertificateException {}
                public void checkServerTrusted(X509Certificate[] chain,
                                               String authType) throws CertificateException {}
                public X509Certificate[] getAcceptedIssuers() {
                    return new X509Certificate[0];
                }}}, new SecureRandom());
            HttpsURLConnection.setDefaultSSLSocketFactory(
                    context.getSocketFactory());
        } catch (Exception e) { // should never happen
            e.printStackTrace();
        }
    }

or check system date of your device - I had this Exception when I tried to connect with wrong date!..

I tried release an update with such code and release was blocked by Google by security reasons. — Vadim, Aug 01 '19 at 08:04

score 7 · Answer 8 · answered Aug 17 '20 at 13:41

7

If anyone come across this issue pertaining to specific device, then the reason should be because of incorrect date set in the device.

answered Aug 17 '20 at 13:41

harishanth raveendren

534
5
8

score 6 · Answer 9 · answered Nov 03 '21 at 06:59

6

I fixed this error by resetting my emulator date and time. My server is working fine just I changed the date and time of my emulator as current server time zone.

answered Nov 03 '21 at 06:59

Sachidanand Pandit

328
6
10

score 2 · Answer 10 · answered Jul 17 '22 at 13:32

2

If you use android emulator, you can wipe data and run again, it works

answered Jul 17 '22 at 13:32

Muhammed Murat Göktaş

67
5

This worked for me, after wiping my data – Onalo Joseph Sep 01 '23 at 23:20

score 1 · Answer 11 · answered Oct 17 '21 at 10:08

@Yash Bhardwaj in the comment on @Vadim answer said that the problem was in Glide framework. I faced the same problem: Https requests to server using Ktor framework were all successful, but when Glide tried to load image from the same server, it faced the SSLHandshakeException. To solve this issue you should look here: Solve Glide SSLHandshakeException.

To make a deal with @GlideModule annotation you should import kapt plugin and add these dependencies into your app build.gradle:

implementation 'com.github.bumptech.glide:okhttp3-integration:4.11.0'
kapt 'com.github.bumptech.glide:compiler:4.12.0'

score 0 · Answer 12 · answered Jul 19 '23 at 09:36

0

In my case the date/ time was ok and I was still getting the exception. I restarted my device and the problem went away. Hope it helps someone if all the above fails.

answered Jul 19 '23 at 09:36

android enthusiast

2,062
2
24
45

SSLHandshakeException - Chain chain validation failed, how to solve?

12 Answers12

Linked

Related