-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Illegal SNI hostname when using self-signed certificate #1032
Comments
Oh, I found this rustls/hyper-rustls#56 is related |
I changed to native-tls with no luck:
It fails with
Is it the problem with the certificate I generated? I used this two commands:
I also tried method on this blog to generate the cert |
Ok, I found a working version
|
@snify This is not a solution because you are using |
@shirshak55 I agree with you, It would be great to accept the self-signed certificate, I didn't find a way though. |
I have a server developed with
actix-web
using self-signed certificate. When usingreqwest
to query the api, server responds with:I have no trouble using
curl -k ....
or postman, I don't know how to configure reqwest to make it behave likecurl -k
.What I have tried
danger_accept_invalid_certs(true)
onClientBuilder
native-tls
feature and calldanger_accept_invalid_hostnames(true)
onClientBuilder
add_root_certificate(cert)
to add the server's certificaterustls-tls
feature and use rustls and disable sni like thisThe text was updated successfully, but these errors were encountered: