I'm currently encountering an issue when using the Guzzle 
<https://github.com/guzzle/guzzle> (version >= 4) library on google app 
engine.  It appears as though any time I try to use the library, I get the 
following message: 

*"No system CA bundle could be found in any of the the common system 
locations.*
*PHP versions earlier than 5.6 are not properly configured to use the 
system's*
*CA bundle by default. In order to verify peer certificates, you will need 
to*
*supply the path on disk to a certificate bundle to the 'verify' request*
*option: http://docs.guzzlephp.org/en/latest/clients.html#verify."*

This error is just a static message 
<https://github.com/guzzle/guzzle/blob/e63c583a936fa7304eab02aa7826d8df157d3330/src/functions.php#L192>
 
that guzzle maintains whenever it's unable to determine a certificate to 
use during secure connections.

I have a ticket 
<https://code.google.com/p/googleappengine/issues/detail?id=12178> open in 
the google app engine bug tracker regarding this (if anyone is able to add 
the *php* tag to it, please feel free).  I guess the issue at this point is 
that regardless of whether I'm using cURL, cURL lite or the stream wrappers 
(all of which guzzle will attempt to use), I'm always confronted with an 
error accessing SSL addresses.

Has anyone been able to get around this, or is this something the google 
apps team can look into?  I have an app I'd really like to be able to start 
getting some of my testing users on, but can't until this is resolved.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/eb92cf0c-ce25-4d5e-92bc-579e2a8d8031%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to