Peer certificate cannot be authenticated with given CA certificates about gmailr HOT 7 CLOSED

@jimhester: an additional possibility that too many packages ignore: in enterprise and government environments, users often must use custom CA bundles provided by their IT. Having a well documented example in the package docs that shows how to successfully point to a custom certificate file would be beneficial.

from gmailr.

I have finally managed to get rid of this error by running first (don't ask me why it fixes it, I have found this on another forum, for a slightly different problem)

httr::set_config( config( ssl_verifypeer = 0L ) )

Should we include this in gmailr?

from gmailr.

httr::set_config( config( ssl_verifypeer = 0L ) )

don't ask me why it fixes it

Seems very much like you're disabling peer verification which would not be the right way to go.

from gmailr.

httr uses curl, not RCurl so you need to update the curl package. However the error you are getting looks to me like your CA certificates are either not being found appropriately or are outdated in your OS.

If updating curl does not fix the issue I would open an issue at https://github.com/jeroenooms/curl/issues/.

In either case I don't believe this is a gmailr issue.

from gmailr.

I had a similar problem with a different site and your fix worked as well. The issue is that the target site's SSL chain is screwed up somehow and httr rejects a connection accordingly. Your fix tells the system "don't worry about it."

from gmailr.

Mine was cause because of incorrect system date and time. If that's the case you just have to change your computer date and time to the real one.

from gmailr.

@WilDoane, I agree with you, having a well documented example would be great, however I do not know what the best practice for how to do this is, nor the local setup to reproduce and test the suggested fixes.

I think a combination of CURL_CA_BUNDLE and CURL_SSL_BACKEND environment variables can be used to configure the proper bundles for your system in the curl package, but really I think the best place for this documentation in the curl package, not in gmailr.

from gmailr.