-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when making call from client to server #15
Comments
Hi, Thank you for reaching us. It seems like the certificate keychain used by Please let us know if you need more help with this issue. Best, On Wed, Apr 1, 2015 at 8:46 AM, Tommy Nguyen notifications@github.com
|
I have followed your steps and also searched google for further help but to Can you please help me, the api still dont work 2015-04-01 14:53 GMT+02:00 Tommaso Barbugli notifications@github.com:
|
1, Download the Certficate Authority Bundle and save it somewhere locally. Full example:
I hope this helps somebody. |
David's suggestion is correct. I am going to add support for options to be On Tue, Apr 28, 2015 at 1:10 PM, David Hancock notifications@github.com
|
hi, no @davgothic it's not solve my problem. thanks. |
@MasterB can you elaborate a bit more? |
@tbarbugli I've updated Guzzle from 5 to 6. Now its not possible to connect to my https - API, which has a Sneakoil certificate installed. I use PHP 5.5.x. Maybe there is a config problem with the server. I've tried some things without success. Simple 'verify' => false no longer works for me. http://docs.guzzlephp.org/en/latest/request-options.html#verify-option I'm not an SSL certifacte expert. |
I've seen on the class GetStream\Stream\Feed that a new GuzzleHttp\Psr7\Request is made, and it has $this->guzzleOptions as fifth parameter. |
@sabrinapisol You're right! I created this PR #45 which should fix that! It's probably a remainder of upgrading from Guzzle v4-5 to Guzzle v6. I would be happy if you could take a look at that PR and tell me if you spot any mistakes. |
@MasterB also for you, #45 should fix that. Could you let me know if it works if you install it using
(please don't commit that, but only run it locally) and then execute the usual $feed->setGuzzleDefaultOption('verify', '/absolute/path/to/cacert.pem');
// or:
$feed->setGuzzleDefaultOption(GuzzleHttp\RequestOptions::VERIFY, '/absolute/path/to/cacert.pem');
// see: http://docs.guzzlephp.org/en/stable/request-options.html#verify Thanks! |
@sabrinapisol @MasterB Replaced #45 with #49. |
Fixed in 2.4.1 |
Fatal error: Uncaught exception 'GuzzleHttp\Ring\Exception\RingException' with message 'cURL error 60: SSL certificate problem: self signed certificate in certificate chain' in C:\workspace\app\vendor\guzzlehttp\ringphp\src\Client\CurlFactory.php:126 Stack trace: #0 C:\workspace\app\vendor\guzzlehttp\ringphp\src\Client\CurlFactory.php(90): GuzzleHttp\Ring\Client\CurlFactory::createErrorResponse(Object(GuzzleHttp\Ring\Client\CurlHandler), Array, Array) #1 C:\workspace\app\vendor\guzzlehttp\ringphp\src\Client\CurlHandler.php(78): GuzzleHttp\Ring\Client\CurlFactory::createResponse(Object(GuzzleHttp\Ring\Client\CurlHandler), Array, Array, Array, Resource id #68) #2 C:\workspace\app\vendor\guzzlehttp\ringphp\src\Client\Middleware.php(54): GuzzleHttp\Ring\Client\CurlHandler->__invoke(Array) #3 C:\workspace\app\vendor\guzzlehttp\ringphp\src\Client\Middleware.php(30): GuzzleHttp\Ring\Client\Middleware::GuzzleHttp\Ring\Client{closure}(Array) #4 C:\workspace\app\vendor\guzzlehttp\guzzle\src\RequestFsm.php(129): GuzzleHttp\Ring\Cli in C:\workspace\app\vendor\guzzlehttp\guzzle\src\Exception\RequestException.php on line 51
I would appreciate if you could help me get around this error
The text was updated successfully, but these errors were encountered: