nginx HTTPS reverse proxy causes the client to fail to connect to server in unintuitive way
See original GitHub issueHi,
Electrum Wallet 3.3.4 on OSX, same problem on Windows.
I’m testing an instance of electrum server. Everything works well when using it in clear (http port 50001) as well as through Tor, but when I use it with TLS (I installed a letsencrypt TLS certificate), Electrum wallet always gives me this error:
[i][electrum.kexkey.com] disconnecting due to: SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)')
Used -s electrum.kexkey.com:50002:s
when starting up.
Are you aware of any recent TLS problems with python or electrum wallet? When I hit https://electrum.kexkey.com on port 443 or 50002, the browser tells me the certificate is valid.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:18 (8 by maintainers)
Top Results From Across the Web
Avoiding the Top 10 NGINX Configuration Mistakes
We help you avoid the 10 most common NGINX configuration errors, explaining the problems caused by each and how to fix them.
Read more >What is wrong with my nginx reverse proxy configuration, with ...
First, check if the spinning is client-side or server-side: access it with cURL or turn on web developer tools on your browser and...
Read more >How to use Nginx as a Reverse proxy for HTTPS and WSS
An SSL certificate is a data file hosted in a website's origin server. SSL certificates make SSL/TLS encryption possible, and they contain the ......
Read more >Nginx reverse proxy error:14077438:SSL SSL_do_handshake ...
Seeing the exact same error on Nginx 1.9.0 and it looks like it was caused by the HTTPS endpoint using SNI. Adding this...
Read more >Configuring an Nginx HTTPs Reverse Proxy on Ubuntu Bionic
Installing and configuring Nginx · Update the APT package cache and install the Nginx web server via the package manager. · Disable the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Your port 50002 points to an nginx HTTP webserver. Of course Electrum cannot connect… It should point to the JSON RPC endpoint of an electrum server.
Compare
electrum.qtornado.com:50002:s
with
electrum.kexkey.com:50002:s
I’ve tried connecting to electrum.kexkey.com:50001 using TCP, there I get:
[i][electrum.kexkey.com] disconnecting due to: ConnectionRefusedError(111, "Connect call failed ('158.69.33.222', 50001)")
I’ve also tried electrum.kexkey.com:50002 using SSL, there I get:
[n] couldn't launch iface electrum.kexkey.com:50002:s -- TimeoutError()
I’ve assumed you turned off the server. Reaching a timeout does not suggest SSL related errors. Are you sure your server is on, listening on that port, and that port is open?
It does that! Electrum is very flexible here, as explained in my link above, it accepts both CA signed certs and self-signed certs.
You shouldn’t fiddle too much with the stuff in the certs dir (for the client); apart from maybe deleting files already there, for debugging purposes.