Electrum Server in myNode not providing SSL connection on port 50002 #360
Comments
|
Try upgrading to the latest version and regenerating your electrs certificate via the settings page. |
|
Thank you
Full log below: |
|
OK, it looks like some changes I made for HTTPS certs broke electrs certificate generation. I have some fixes in for release in v0.2.12 that should help. I was able to reproduce the issue with a certificate re-generated using v0.2.11. |
|
Can you retest this with the latest version? |
|
Will do. Might be a few days. |
|
Hi @tehelsper still an error, with latest version of mynode 2.1.3 and fully synched electrs. Something wrong with ssl. |
|
I'm starting to think some clients are pickier about the cert than others for some reason. Which OS are you on? Can you try and connect from a phone or different PC? I can connect from a Windows client and Ubuntu. |
|
Hi @tehelsper Electrum 4.0.2 is running on MacOS (latest version). I don't have windows or another device at the moment. I will try to borrow one or otherwise set something up. |
|
I have the same issue. Latest version of mynode and running electrum 4.0.2. I have had this issue since electrum 4.0 and the last few version of mynode. Electrum will not connect. |
|
additionally, bluewallet on latest iOS will connect but no version of electrum. Perhaps that helps with the troubleshooting here. |
|
Have you tried installing Electrum wallet v3 again to see if it connects? I've tried on both 3 and 4 and can connect on all combinations I have tried. |
|
I installed 3.3.8 again. Completely removed electrum 4.x and all wallet files. I recreated a monitor only wallet (for time sake), plugged in the xpub and it still cant connect. :(. Again, bluewallet on ios is able to connect to mynode. it seems to be something about the new version(s) of mynode and electrum. This all worked just fine until a few releases ago. Now that it still happens on 3.3.x electrum, i think it must be something with mynode/electrs? I cant consistently recreate the problem. I am also running mynode from virtualbox on linuxmint (with all updates). Perhaps theres an issue with the VM version of mynode?
This github issue you pointed me to seems very similar:
#360
Thanks for any additional help on this!
Kyle
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Tuesday, August 4, 2020 6:05 PM, Taylor Helsper ***@***.***> wrote:
Have you tried installing Electrum wallet v3 again to see if it connects? I've tried on both 3 and 4 and can connect on all combinations I have tried.
—
You are receiving this because you commented.
Reply to this email directly, [view it on GitHub](#360 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AQP2L32MIOFW6OAOZ2QDXKLR7CV6JANCNFSM4O6PJUQA).
|
|
“I *can* consistently recreate the problem” (edit).
Sent from ProtonMail Mobile
…On Tue, Aug 4, 2020 at 10:33 PM, tripletuple ***@***.***> wrote:
I installed 3.3.8 again. Completely removed electrum 4.x and all wallet files. I recreated a monitor only wallet (for time sake), plugged in the xpub and it still cant connect. :(. Again, bluewallet on ios is able to connect to mynode. it seems to be something about the new version(s) of mynode and electrum. This all worked just fine until a few releases ago. Now that it still happens on 3.3.x electrum, i think it must be something with mynode/electrs? I cant consistently recreate the problem. I am also running mynode from virtualbox on linuxmint (with all updates). Perhaps theres an issue with the VM version of mynode?
This github issue you pointed me to seems very similar:
#360
Thanks for any additional help on this!
Kyle
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 4, 2020 6:05 PM, Taylor Helsper ***@***.***> wrote:
> Have you tried installing Electrum wallet v3 again to see if it connects? I've tried on both 3 and 4 and can connect on all combinations I have tried.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, [view it on GitHub](#360 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AQP2L32MIOFW6OAOZ2QDXKLR7CV6JANCNFSM4O6PJUQA).
|
|
Me too. It never works anymore on 50002. I've an electrumx server on another machine and it works fine. I'll stick with that 🙂 until this is resolved. |
|
I can connect to electrum server on 50002 from my mac, however all mynode https are inaccessible from macOS and android. Is this a known issue? |
Finally, what is the error you see? Does it indicate no response or invalid certificate? |
|
Android 7.1.1 Chrome error is as follows: `This site can’t be reached192.168.2.152 refused to connect. Checking the connection Safari error is in below image Thank you! |
|
Could this be a specific issue with the virtual machine version of mynode? Again, i have wiped, reinstalled the vm version from the website (its really old so it then has to upgrade), and fully upgraded mynode to the latest version and electrum 3.x and 4.x cant connect. I have tried all of the suggestions above as well as the suggestions you made from my original ticket (regen certificate, etc). |
|
Can anyone retest this again after upgrading to v0.2.15? It uses NGINX now for the secure electrum server connection. |
|
Hi @tehelsper Unfortunately still the same error even after upgrade to v0.2.15. Log: |
|
This still does not work for me even after the new update that runs nginx. any clues as to whats going on? |
|
Same for me @tehelsper , is this working for anyone that you know of? |
|
@maltokyo - are you by chance running mynode on a VM via virtualbox? That is my setup and i am having the same problem. I wonder if this is somehow part of the problem otherwise I have to believe that many other users would be raising this issue. I assume running myode as a vm is not the most common deployment and therefore there is not much traction on this issue. |
|
I run it on an old pc ;) amd64. But recently (because if this issue) switched to https://getumbrel.com/ |
RP4 is by far the most common, but there are a decent number of VM users. I have tried resetting and re-syncing a VM version of electrs many times and have not been able to reproduce it. The error comes from a library within electrum client for validating the cert - I'm not really sure what to do, especially if other clients can connect. Have you tried a totally fresh VM to see if that changed anything? |
|
Yea I did that and I did it by downloading a fresh copy of the ova and installing it and then going through the upgrades to get to the current version at the time and still had the same problem. I also spun up a new vm with the latest version after you updated the ova's from the mynode website - still the same problem. |
|
@tehelsper any way to help us open an issue for the electrum devs to maybe take a look since it seems to be affecting electrum only? |
|
@tripletuple Good idea - I should have logged one a while ago. Here's a link if you want to add any more info: I don't think electrs, the certificate, or nginx is the issue based on how frequently it works for other users and is running properly on port 50001, so I logged it with the electrum client project. |
|
ACK. Thanks! |
|
It also doesnt work on 50001. Does that change anything? |
|
Ah, yeah, it would for you. The original issue indicated 50001 works ok. What happens when you try port 50001? |
|
Same issue. Electrum 3.x or 4.x cant connect to ex: 192.168.100.x:50002 or 192.168.100.x:50001. |
|
Are you updating the config file to ensure is it not attempting a secure connection on port 50001? You can't just update it in the UI. What does this command show? sudo journalctl -r -u electrs |
|
A lot of this: Oct 29 08:34:15 mynode electrs[4986]: 2020-10-29T08:34:15.536-05:00 - TRACE - RPC PeriodicUpdate with the occasional: Oct 29 08:47:15 mynode electrs[4986]: 2020-10-29T08:47:15.308-05:00 - DEBUG - applying 1 new headers from height 654663 |
|
Im just updating the UI. Thats always worked in the past since before this issue cropped up a few releases ago. I also have this same setup on another VM except running mint with bitcoin core/electrum personal server and connecting to that node works over 50001 or 50002. |
|
Hmmm.... That info looks like it is running fine. Can you try updating the config file? You should need to change the "t/s" letter at the end. |
|
I cleared the certs using that debug page and all is well now! Thanks man. |
|
@maltokyo Did you ever use a different device to try and connect on port 50002? I still think this is on the client side caused by certificate confusion. |
|
Yes I tried electrum on Android too. Couldn't connect. All of them connect flawlessly to electrum server in Umbrel |
|
One thing to note about this issue is that if the mynode VM gets rebooted, you have to go through the process to clear the certificates every time on the local machine where you are running electrum. Is there a way to fix this permanently? |
|
I have a similar problem, I use a MacOS and mine ( Electrum ) does not connect.
|
|
I have the same problem with EPS. I removed the EDIT: nvm the problem was in EPS side - chris-belcher/electrum-personal-server#286 (comment) |
Can only connect on non-encrypted 50001 port, but I cannot connect with 50002.
Details here in an issue raised on electrs GitHub, but as you can see they asked me to post here as they said it is a myNode issue:
romanz/electrs#275
The text was updated successfully, but these errors were encountered: