Running Electrs 0.11.1 on StartOS 0.4. Electrum 4.7.1 on macOS can’t connect over LAN or Tor.
What I’ve confirmed:
Electrs logs show it’s running and synced on 0.0.0.0:50001
LAN port 51036 is reachable and TLS certificate verifies correctly
Tor onion address is reachable (SOCKS5 request granted)
Electrum JSON-RPC handshake (server.version) gets no response on either path
Did something change in how Electrs is exposed in 0.4? Any known issues with Electrs connections after the upgrade?
Did you install Tor?
Did you verify the .onion interface or create a new one?
I did install tor and created an onion services both http and https
I also tried connecting thru the local ip.
You’ll need:
99% of complaint about not being able to connect to a server’s electrs interface I’ve ever seen are due to Tor being Tor, and are fixed with repeated re-connections, restarts and prayers.
Now, if you can’t connect via the IP address and Port, then there’s either something wrong with Electrs (and it will appear in the logs of Electrs) or something wrong with Sparrow or the connectivity of your network. I don’t know where to tell you to start looking there, as these are things only you will know.
With regards to your original question, and how it’s relevant here – whether anything has changed with Electrs on 040 – yes, it has been made much much easier to connect to in many more ways. With that in mind, there almost certainly has to be a small easily missed mistake in what you’re pasting, typing or clicking.
Thanks. Just to clarify, this was working before the 0.4.0 upgrade.
I am using Electrum on my laptop, with the same client setup as before. The main thing that changed was the server upgrade. After upgrading to 0.4.0, the Electrs connection stopped working.
I have already tested connecting to the server, and that works fine, so basic connectivity does not seem to be the issue.
I am now installing Fulcrum to see if that works, but with Electrs it is currently not working.
So I do not think this is simply a case of using the wrong client or not knowing how to connect. The same Electrum client was working prior to the upgrade. What I am trying to isolate is what changed on the server side after 0.4.0 that could have broken the Electrs interface.
Every single aspect of everything you can possibly imagine has changed. StartOS v040 is a completely different operating system. Nothing survived. The Electrs service you are running, provided you updated that too, is also 100% different. It has an interfaces section, with interfaces made available; new interfaces completely unrelated to the ones you had previously. This means you set up Sparrow’s connection again, wiping out any old connection settings you had. You can do it with IP and port, mDNS domain and port, or various types of remote or local domains or TOR if you set that up.
If you think there’s a bug in Electrs that no-one else has found.… its a possibility… but it would be something with the Electrs service itself rather than the networking stack of StartOS which everyone is using with all the services and seems to work fine. If there’s something on your network/router blocking ports, that would be something to look at too.
Not sure what it was, but the problem has been fixed with the latest update to Beta9.
I had some similar issues with my LND not connecting to Electrs. I’m not sure which update may have caused this. But I found that the RCP passwords for Core, Elecrts were different to LND. Super weird. Also, there were some connection issues with the IP Addresses in /lnd/data/main/tls.cert
ChatGPT’d my way through it. And it seems to be working now. Hopefully didn’t handover all creds to Open AI.