-
Notifications
You must be signed in to change notification settings - Fork 79
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
OpenSSL::SSL::SSLError while using LetsEncrypt ssl certificates #333
Comments
Please update, we released a version (v9.16.3) earlier this evening to fix this bug - can you please confirm if it fixes your problem? |
v9.16.3, it is still failing for my case:
Output:
|
I've just checked that it supports allowing disabling of the certificate as per pact-foundation/pact-ruby-standalone#69 (comment), but it should also support the OpenSSL standard SSL_CERT_FILE or SSL_CERT_DIR env vars. See also the upstream ticket: pact-foundation/pact-ruby-standalone#69. I think it might need a separate solution to get the correct CA into the bundle, stay tuned. |
@TimothyJones going to pin this issue whilst we sort the situation out. |
Finally made it work with Thanks a lot @mefellows for the support! |
Thank you for confirming Misha! |
|
It looks like this is not yet available in the latest version of the client library
It works like a charm! Thanks a lot @mefellows 🙏 |
Great, thanks for clarifying! A clean install should bring in the right version, we only pin to the major version: https://github.com/pact-foundation/pact-js/blob/4c949aec080472ea18d883468e705918a5389430/package.json#L97 |
Clean as in without any lock-files. Possibly we should put that in the documentation.
…Sent from my mobile
On 11 Oct 2021, at 7:18 pm, Matt Fellows ***@***.***> wrote:
Great, thanks for clarifying!
A clean install should bring in the right version, we only pin to the major version: https://github.com/pact-foundation/pact-js/blob/4c949aec080472ea18d883468e705918a5389430/package.json#L97
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Software versions
Issue Checklist
Please confirm the following:
Expected behavior
The client should establish an HTTPS connection to the Pact Broker
Actual behavior
Client fails to verify SSL certificates
Steps to reproduce
@pact-foundation/pact
library to establish an HTTPS connection with Pact broker.Details
It seems that pact is using Ruby HTTP client under the hood, which is reported for having outdated SSL certificate files bundled inside the library.
In the httpclient issue, it is recommended to monkey patch HTTP client library to use system default SSL certificates.
The text was updated successfully, but these errors were encountered: