Trezor troubleshooting

Trezor hardware devices are compatible with Casa Multisig. 

Casa supports both the Trezor One device, as well as the Trezor Model T. See our list of supported devices for a full list of the devices we support.

Whether you are adding the Trezor, doing a health check, or sending funds from your Casa multisig keyset, you interact with the Trezor API, a web interface that allows you to easily add a signature to your keyset. 

Depending on your browser settings the web interface may have trouble recognizing your Trezor if you have not downloaded the Trezor Bridge. 

See this article for a detailed explanation of the Trezor Bridge.

Another troubleshooting step is to download Trezor Suite App to your desktop or laptop and keep it open during your health check or transaction signature. 

You can download Trezor Suite here! 

Some common Trezor errors are: 

"Health check failed. This device is not part of your wallet."

Possible solutions: Make sure you are using the correct Hardware device to sign that transaction or Health check.

If you are using passphrase protection on the device, you will need to enter that passphrase when prompted, or otherwise leave it blank if you are not using passphrase protection for your Casa key.

“TrezorConnect is not defined/is undefined”

Possible Solutions: Try another cable. Not all USB cables are rated for data transfer, so make sure that the USB cable you're connecting is the one that came with the Trezor, or is otherwise rated for data transfer (and not just a charging cable).

Make sure to close anything else that would also be trying to communicate with the Trezor such as a watch-only wallet like Electrum

Another thing to look at is seeing if you need a firmware update. You can check this article for the recent supported firmware.

“Session not found”

Possible solutions: Please make sure that there are no ad blockers or a privacy browser setting can trigger this error. Things like Privacy Badger should be turned off.

If you've tried the above steps and are still having issues, please reach out to our support team, and we're happy to assist. 

“Interaction Timeout”

This can happen if you are attempting to sign a transaction with too many inputs. If this happens, you can always try to recreate a smaller transaction, or a transaction that spends from fewer UTXOs in your keyset. Casa App does have the ability to spend from specific addresses. See: Spending from Specific Addresses

 

“Hanging window (non responsive window)"

Possible solutions: Try a different browser or try to clear your cache. 

 

 

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share