Troubleshooting

This page might be outdated due to the Shelley update!

Hardware Wallets

General troubleshooting steps you should try before contacting us

• Disable all ad-blockers on AdaLite
• Update you Trezor/Ledger firmware and Ledger apps to the latest versions
• Try to initialize Ledger on AdaLite both in Chrome and Firefox browsers in Incognito(Chrome)/Private(Firefox) mode
• If the initialization is interrupted with Windows Security Verification pop-up, ignore this and continue (or even try to move the popup away by dragging - interaction with the popup will cancel the connection with Ledger
• Try using your hardware wallet on https://myetherwallet.com or other web wallet supporting your hardware wallet. If it does not work there as well, it is probably a generic problem not related to AdaLite and we would recommend you contacting first the hardware wallet's vendor support (explaining that you have problems on more than one web wallet).

"Wallet initialization error" or stuck on "Waiting for Commands..." while connecting with my Ledger Nano S/X

• If you are on a Linux system, please check that you have the proper udev rules set. To set them, we recommend you to download this repository: https://github.com/LedgerHQ/udev-rules and executing ./add_udev_rules.sh in the downloaded folder.

• On Windows 10 (build 1903) there are reports about AdaLite not working with Ledger Nano S/X. This is a general Ledger problem, you can find suggested solutions in the following article: https://www.ledger.com/your-ledger-device-and-the-upcoming-windows-10-update Basically, make sure you have the latest Ledger firmware version and if you see a popup prompting you to interact with your U2F device, you can ignore it and move it aside, it does not prevent AdaLite nor Ledger from functioning as expected. If you still experience problems, don't hesitate to contact us (please include your OS and browsers versions). This is a temporary problem that will be solved once Ledger developers release an update that will allow us to seamlessly switch to a different communication protocol.

"Firmware error" while signing a transaction with Trezor Model T

• This is a known issue (https://github.com/trezor/trezor-firmware/issues/94) which stems from non-optimal processing of big (in terms of byte size) transactions on the Trezor firmware for Cardano. A workaround, for now, is sending multiple transactions, involving smaller amounts of ADA which should result in smaller transactions with fewer inputs, processable by Trezor.