Closed pingec closed 2 years ago
Are you using any other software that might communicate with Trezor while you are signing TX with Electrum? (such asBrowser with wallet.trezor.io or suite.trezor.io open, a Trezor Connect enabled wallet or Trezor Suite desktop app)
I do not think so, none of the mentioned apps nor websites were open or running. I now tried again with my main browser closed and opening a browser I have never used for any crypto wallet operations and I opened only the bridge status page in it.
From the bridge status page I saw that the session status was "no session" until I started signing a transaction with electrum, at that point the session status changed to a number and finally when electrum showed that error again, the session was again showing "no session".
We are releasing bridge 2.0.30 soon - will you please test the binaries from https://wallet.trezor.io/data/bridge/2.0.30/index.html and let us know whether this helped?
I have tested and I the issue is still there
Same issue here.. it's frustrating.. and what's with the long long signing times (that's actually if it doesn't fail half way) Trezor one 2/3 500 byte transactions and higher Latest trezor bridge 2.0.27 Latest electrum 4.1.2
this seems to be the same thing as https://github.com/trezor/trezord-go/issues/247
I am closing this as a duplicate of https://github.com/trezor/trezord-go/issues/247
Even though this issue is older the other one contains more useful information.
Hello,
I initially opened this issue at https://github.com/spesmilo/electrum/issues/6684 but was told this is likely a bridge issue, so I am reporting it here as well.
I am trying to use:
When I try to sign a multisig transaction (usually they are large eg. 100-200 inputs) the signing will mostly fail with the following message:
TransportException('trezord: release/10 failed with code 400: session not found')
The trezor signing takes a long time (many minutes) and sometimes this error will show up almost immediately, sometimes it will show up after a while and sometimes there is no error and the signing actually succeeds. It fails about 80% of time.
Using webusb instead works just fine without any issues.