Quantcast
Channel: Active questions tagged https - Stack Overflow
Viewing all articles
Browse latest Browse all 1486

Connecting to tokio-native-tls echo.rs from react

$
0
0

I upgraded my react front end to use https. That broke the connection to my backend tokio socket server. I tried to run a test against the tokio-native-tls echo.rs example which uses an identity.p12 file after I ran these commands:

openssl pkcs12 -in identity.p12 -nocerts -out .conf/server.keyopenssl pkcs12 -in identity.p12 -clcerts -nokeys -out server.crtopenssl rsa -in server.key -out .conf/server_d.keySSL_CRT_FILE=.cert/server.crtSSL_KEY_FILE=.cert/server_d.keyHTTPS=true

Front end runs under nginx which I configured to use https.

thread 'main' panicked at 'accept error: Ssl(Error { code: ErrorCode(1), cause: Some(Ssl(ErrorStack([Error { code: 336151574, library: "SSL routines", function: "ssl3_read_bytes", reason: "sslv3 alert certificate unknown", file: "../ssl/record/rec_layer_s3.c", line: 1528, data: "SSL alert number 46" }]))) }, X509VerifyResult { code: 0, error: "ok" })', tokio-native-tls/examples/echo.rs:33:34

I'm having trouble configuring the react client with the server using that identity.p12 file. Any help would be appreciated.


Viewing all articles
Browse latest Browse all 1486

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>