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.

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

Issue connecting to server with self-signed certificate #118

Open
hisenb3rg opened this issue Sep 21, 2023 · 0 comments
Open

Issue connecting to server with self-signed certificate #118

hisenb3rg opened this issue Sep 21, 2023 · 0 comments

Comments

@hisenb3rg
Copy link

I'm using electrum-client through bdk-cli and trying to securely connect to local electrs with self-signed certificate. I have set the this certificate as trusted in system keystore, but it didn't help.

Is there an option (env var) to set the system keystore as CA store? Or any other way around this issue?

Here's the log output from bdk-cli:

[2023-09-21T19:09:49Z INFO  electrum_client::client] Succesfully created new client
[2023-09-21T19:09:49Z DEBUG rustls::client::hs] Using ciphersuite TLS13_AES_256_GCM_SHA384
[2023-09-21T19:09:49Z DEBUG rustls::client::tls13] Not resuming
[2023-09-21T19:09:49Z DEBUG rustls::client::tls13] TLS1.3 encrypted extensions: []
[2023-09-21T19:09:49Z DEBUG rustls::client::hs] ALPN protocol is None
[2023-09-21T19:09:49Z WARN  rustls::conn] Sending fatal alert BadCertificate
[2023-09-21T19:09:49Z WARN  electrum_client::client] call 'batch_script_get_history' failed after 6 attempts
[2023-09-21T19:09:49Z ERROR bdk_cli] Electrum client error: Made one or multiple attempts, all errored:
    	- invalid peer certificate contents: invalid peer certificate: UnknownIssuer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant