the "no reply from server" message is new indeed, but the behaviour is mostly unchanged.
perhaps the timeout is to short for tor
Topic: Serious Bug in Electrum (Read 602 times)
Yes, that's what I thought as well.
But when i first encountered this issue it did send the transaction a 2nd time. (it was a transaction to another one of my own wallets so no problem at all).
I am 100% sure about it.
And the "no reply from server" happens quite often since the upgrade. (every third or fourth tx) I use tor as a proxy which might be the reason..but it never happened this way since I use electrum (for years).
Thanks you for your fast reply.
But when i first encountered this issue it did send the transaction a 2nd time. (it was a transaction to another one of my own wallets so no problem at all).
I am 100% sure about it.
And the "no reply from server" happens quite often since the upgrade. (every third or fourth tx) I use tor as a proxy which might be the reason..but it never happened this way since I use electrum (for years).
Thanks you for your fast reply.
there is no risk of paying twice if the server does not answer.
if your wallet did not receive the transaction, it will retry to send the same coins.
if your wallet did not receive the transaction, it will retry to send the same coins.
Hi,
I noticed since upgrading to 2.6 ( and now upgraded to 2.6.2) often I get the message "no reply from server" when sending a tx block.
BUT they funds have been sent though the Pay to field and the other fields are not being cleared.
It gives the impression the tx did not go through but it did. I catched it early enough but others may not and send their transactions twice or more.
Please look into this as soon as possible.
Thank you for all your great work!
EDIT: the sent tx is visible after the next sync or restart.
I noticed since upgrading to 2.6 ( and now upgraded to 2.6.2) often I get the message "no reply from server" when sending a tx block.
BUT they funds have been sent though the Pay to field and the other fields are not being cleared.
It gives the impression the tx did not go through but it did. I catched it early enough but others may not and send their transactions twice or more.
Please look into this as soon as possible.
Thank you for all your great work!
EDIT: the sent tx is visible after the next sync or restart.
Jump to: