search

floating / frame

System-wide Web3 for macOS, Windows and Linux
https://frame.sh
GNU General Public License v3.0
1.09k stars 151 forks source link

Trezor One does not connect #1694

Open john-light opened 10 months ago

john-light commented 10 months ago

After connecting a Trezor One and entering the PIN (and passphrase, if needed) Frame throws an error: Please reconnect this signing device. Clicking Reload signer results in a spinning wheel and doesn't fix the problem.

To isolate the problem to Frame I have confirmed that Trezor firmware is up to date, Trezor Bridge is running, and I am able to use the Trezor with Trezor Suite desktop app and other applications (e.g. MetaMask).

Frame version: 0.6.8 OS: Linux Mint 20.3

Screenshot from 2024-01-11 13-46-56

matmilbury commented 9 months ago

Happened to me too.

Opened logs at ~/.config/frame/logs/main.log and found could not open Trezor Error: All backends are down error.

This led me to https://trezor.io/support/a/discovery-error-issue

And in my case it was due to my VPN connection.

I connected to a different random VPN server and it fixed the issue for me.

john-light commented 6 months ago

Thanks @matmilbury for the suggested fix. I am still having the issue. I have used other wallets with Trezor e.g. Enkrypt and MetaMask, and Trezor works with all of the other wallets I have tried. Only Frame is having this issue. So I think it's worth keeping this issue open. It would be great if someone can figure out how to make Trezor work even if some users are on a VPN (if that is actually the root cause of the problem) since other wallet developers have been able to do this. I really would like to be able to use Frame with Trezor again, and to be able to recommend Frame to other Trezor users as well.

mente371 commented 6 months ago

For 2 days, I have the same problem. I note that all the PYLON RPC connections fail. Which seems to induce the failed connection of the signer. Manually changing the RPC addresses doesn not resolve the issue for the signer connection.

danilych commented 5 months ago

Happened to me too.

Opened logs at ~/.config/frame/logs/main.log and found could not open Trezor Error: All backends are down error.

This led me to https://trezor.io/support/a/discovery-error-issue

And in my case it was due to my VPN connection.

I connected to a different random VPN server and it fixed the issue for me.

Changing of the VPN server works for me, thanks <3

Crypt0-Bear commented 2 weeks ago

Can you set a system proxy for frame to connect to the trezor backend? If this is a connectivity issue then hopefully getting to use a specific proxy could prevent this issue even when on vpn