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
Not Connected. Ever. v2.7.9 on Tails v2.10 #2146
Comments
maybe the server is not online anymore? |
@radbradsdad, seen your message, I have checked out Electrum 2.7.9 with Tails 2.10, and it connects and syncs fine here (2.7.9 is the version coming with Tails 2.10).
I'm using it through Tor, the network configuration is the default one
for Electrum in Tails:
Select server automatically: check (= activated, do it automatically)
Use SSL: check (activated)
Proxy: SOCKS5 localhost 9050
Be sure to wait a few seconds after booting and logging in, until Tails tells you that Tor is ready to use. If that does not happen, the problem is elsewhere. You might have to look into Tails docs and troubleshoot your connection and/or Tor setup.
It always ran straightforward here, so I have no idea what you might need to change.
At present, I'm actually using Electrum 2.7.18 (*) on Tails 2.10 and it works fine too (just a few messages on the terminal window from which I launch, but it connects and syncs very fast and I can receive and send coins).
I had tried previous Electrum versions (2.6.3, 2.6.4, 2.7.12, 2.7.17) on previous Tails versions, always through Tor, I haven't made many transactions yet but I can tell you that so far I never had one single
connection/sync problem (just one day a momentary "server did not answer" thing while broadcasting a transaction, apparently independent of the Electrum version, but that happened after a straightforward connection and sync, anyway).
(*) The online part: I boot Tails from DVD, then launch a script I prepared, which eliminates the .electrum folder and replaces it from a backed up one (**), it extracs Electrum from a password protected archive, enters its folder and launches it from within (otherwise the Electrum version coming with Tails would be launched) with the appropiate wallet. When Electrum exits, the script offers to backup the .electrum folder. I can launch again and then launch another script which only does that backup (or I can trivially launch tar myself, but the scripts renames previous backups to always keep a few of them).
The offline part: I boot from pendrive, Persistence is active but just to avoid a second pendrive. I launch a script similar to the other one, the only thing which changes is that the wallet is the cold storage one.
So, not modifying anything in Tails nor relying on Persistence more than that, I can switch rather quickly to a new Tails/Electrum version.
Actually, .electrum here is a sym link to something like .electrum_2.7.18, so I can keep different backups and try a previous Electrum version any time.
(**) Upon first launch of a new Electrum version, I only leave the blockchain_headers file in the .electrum folder (or nothing at all), and let Electrum create the rest, and configure again Network and other Preferences.
|
Toporin
pushed a commit
to Toporin/electrum-satochip
that referenced
this issue
Aug 10, 2021
We were on Zbar git master before because we needed the autoconf fix. Since then version 0.23.91 was released which includes the fix. This updates `contrib/zbar` to 0.23.91 (c7d9809b0b49e81fd86a48e9d1bc3c7db8c50bbd) Closes spesmilo#2146
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Electrum 2.7.9 doesn't seem to want to connect despite various config changes. I've tried auto-select server as well as:
Server: 56ckl5obj37gypcu.onion:50002
SSL Enabled
Socks 5, localhost:9050
OS: Tails v2.10
Regardless, the message in the bottom just says "Not connected"
Any help would be appreciated. I sent some btc into the wallet, and there are currently 10 confirmations via blockchain. But nothing in my Electrum wallet.
The text was updated successfully, but these errors were encountered: