-
Notifications
You must be signed in to change notification settings - Fork 1k
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
0.12 reports invalid cert where 0.11 succeeded #1904
Comments
In the original project that led to this report, I was getting |
I expect this is the same issue I ran into with this upgrade, specifically this entry in the 0.12.0 changelog:
This was originally undocumented in the 0.12.0 release notes; the line was added later in #1781. |
The fix is to use one of these methods:
|
Confirmed. Thank you! |
Otherwise you get: ```text Error: setup client Caused by: 0: connect to endpoint 1: transport error 2: invalid peer certificate: UnknownIssuer 3: invalid peer certificate: UnknownIssuer ``` Also see hyperium/tonic#1904 .
Otherwise you get: ```text Error: setup client Caused by: 0: connect to endpoint 1: transport error 2: invalid peer certificate: UnknownIssuer 3: invalid peer certificate: UnknownIssuer ``` Also see hyperium/tonic#1904 .
Bug Report
After upgrading tonic from 0.11.0 to 0.12.2, gRPC connections fail with
InvalidCertificate(UnknownIssuer)
for the exact same server endpoint.Platform
Windows
Crates
tonic
Description
A very trivial repro, comprising just this:
Succeeds when using
tonic
0.11, but fails on 0.12.x.I have the minimal repro ready to
cargo run
at this repo: https://github.com/aarnott/tonic_fail_repro (main
branch works,broken
branch doesn't). The only difference between them is the tonic version.Expected (0.11 behavior)
Actual (0.12.x behavior)
The text was updated successfully, but these errors were encountered: