Google Drive SSL certificate issue happened on v11.27 & 11.29 but not 11.14

[davison]

Yesterday I suffered from failed to login google drive for file sync by windows portable version 11.27. Then I tried to upgrade to 11.29 but still failed.

I google it and forum mentioned that this is related to firewall issue. Below is the discussion in 2019.

viewtopic.php?t=6432

However, I tried to use old version 11.14 and it function properly. I am wondering is it ready related to firewall issue? Anyone suffered the same issue?

Error message is:
Unable to connect to Google Drive. CURLE_PEER_FAILED_VERIFICATION: SSL certificate problem: self-signed certificate in certificate chain [curl_easy_perform]

[Zenju]

"self-signed certificate in certificate chain":

https://stackoverflow.com/questions/54402673/how-to-fix-ssl-certificate-problem-self-signed-certificate-in-certificate-chai

I don't know why 11.27 vs 11.14 makes a difference, though. Perhaps the change is in the Resources\cacert.pem file?

A solution would be to add this "self-signed certificate" to FreeFileSync's cacert.pem.

[davison]

It seems adding "self-signed certificate" to cacert.pem in windows 10 is not a easy task. I tried a shortcut to replacing cacert.pem in Freefilesync 11.27 by 11.14 but problem could not solved. Error message is the same.

I am googling on how to add "self-signed certificate". Thanks for your advice anyway.

To allow more easy for google, the complete error message is:
Unable to connect to Google Drive. CURLE_PEER_FAILED_VERIFICATION: SSL certificate problem: self-signed certificate in certificate chain [curl_easy_perform]

[davison]

Thank you so much for providing me hints.

The problem was solved by manually download the certificate of *.google.com (in .crt format) by browser. Double click .crt file in wins 10 and then install the certificate.

Now, the problem was solved. Thx!!

[davison]

I am sorry to inform you that the problem happened again. It seems related to the expiry of *.google.com certificate. An new certificate was issued since 31 Jan 2023.

But this time the problem could not be solved by include the crt. But version 11.14 is still working.
I am going to download all old portable version, but seems it is not possible. Is there any possible way to do so?

[davison]

I am able to resolve this problem again and several things I did to solve the error.

1. Insert the certificate manually (.crt) as I mentioned previously.
2. Copy and paste the certificate code (.pem) into cacert.pem
3. reboot my PC.

After those actions, I can use freefilesync portable version 12 without error. And I guess this error will happen when certificate failed in Apr)

[xCSxXenon]

This seems like an issue with only one computer/user, no?

[davison]

The answer is yes and no. I can try to work on other PC and tell you the answer.

Yes, it happened on only a PC. This is the only PC using portable version and program run behind a firewall, which is not under my control.