Hi, I’m trying to sign a transaction using my Trezor5 and MetaMask but every time I get to Signature Request and Connect Trezor, I’m getting a message asking me to connect my Trezor even though it’s definitely already connected
I’ve tried all of the different troubleshooting suggestions - i.e. different browser (I’m currently using Chrome, but have also tried Brave), different cable, removing the MM extension and reinstalling, clearing cookies/cache etc. etc. but no luck. My firmware on all devices and Trezor Suite is also up-to-date.
I had this issue a couple of weeks ago when using Brave so I switched to Chrome as suggeted. Up until today, it’s been working fine but suddenly it’s stopped again.
I am dealing with the same issue right now… I don’t want to install the extension on chrome, I’d rather keep my Brave browser. It has been a month of trying things, nothing working. Everything is up to date with firmware, etc. restarted everything, cleared cache multiple times.
I have another friend having the same issue. It’s obviously an issue between MetaMask and Trezor but no-one seems to want to try and fix it. I’m at a bit of a loss as to what to do.
As mentioned, I was using Brave also, but switched to Chrome as suggested, but even Chrome isn’t working now.
We are currently aware of a potential connectivity issue affecting MetaMask. The developers are actively investigating the problem and working on a fix. Unfortunately, I’m not able to provide a specific timeline for when a resolution will be available.
In the meantime, there are a couple of workarounds you can try:
Reinstall MetaMask completely and then reconnect your Trezor. When doing so, please make sure that Trezor Suite is running in the background, as this is required for proper communication with the device.
Alternatively, you can use Rabby or NuFi Wallet. Both are compatible with Trezor and can often be used even on dApps that only display MetaMask as a connection option.
For several days now, I haven’t been able to sign transactions from Google Chrome using the Metamask extension; I don’t use any other browser. When I open a transaction, I see the “Signature Request” box, along with the Cancel and Connect Trezor buttons. When I click Connect Trezor, I get the following message:
"Connect your Trezor
Please continue to ensure that:
Your hardware wallet is properly connected via USB
Try using a different USB cable or port
Restart your device and try connecting again
Your Trezor device is unlocked"
Obviously, I’m doing this with the unlocked Trezor, and the cable works, and the firmware is updated to the latest version (I’ve had this problem since the last update), and the Trezor Suite, Chrome, and Metamask extension are also updated to the latest version.
It seems the Trezor simply isn’t being recognized. Trezor Suite does recognize it, so I think it’s an error between the Trezor, Metamask, Chrome connection… I don’t know.
I’m having the exact same issue with MetaMask and my Trezor Model T. Everything is up to date, unlocked, and connected, but it just loops on the “Connect your Trezor” message.
Rabby Wallet works perfectly fine as a workaround for now. I hope the MetaMask bug gets fixed soon though — I like keeping multiple wallets functional for situations like this.