Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Connecting to a node or cluster via an IP address using TLS results in InvalidDnsNameError #71

Open
shaan1337 opened this issue Jun 22, 2021 · 2 comments
Open

Connecting to a node or cluster via an IP address using TLS results in InvalidDnsNameError #71

shaan1337 opened this issue Jun 22, 2021 · 2 comments

Comments

@shaan1337
Copy link
Member

Sample error when logging is enabled:

DEBUG eventstore::grpc             > Failed to create gRPC channel for candidate Endpoint { host: "172.30.240.11", port: 2113 }: transport error: error trying to connect: InvalidDNSNameError

This occurs due to the following limitation in the webpki dependency:
briansmith/webpki#54

(Parsing IP SANs from certificates is not yet supported)

See also:
rustls/rustls#281
hyperium/tonic#279

This forces the user to use DNS names for each node of the cluster.
@YoEight YoEight removed the cant-fix label Feb 13, 2023
@YoEight
Copy link
Member

YoEight commented Feb 13, 2023

rustls next version 0.21 has fixed that issue. I'll fix it when released.

@YoEight
Copy link
Member

YoEight commented Jan 15, 2024

Waiting on tonic to upgrade to hyper version 1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@YoEight @shaan1337