Rabby Ledger not connecting: how to fix it
Unlock the Ledger, open the Ethereum app on it, close Ledger's own app (Ledger Wallet, formerly Ledger Live), and allow Rabby's request to connect to an HID device. If it still fails, update the Ledger firmware and Ethereum app, try another cable, port or Chromium browser, and reconnect from the beginning.
Quick steps
- Prepare the Ledger. Plug in only one Ledger, enter the PIN and open the Ethereum app until it shows as ready.
- Close Ledger Wallet. Quit Ledger's desktop app (Ledger Wallet, formerly Ledger Live) and any other wallet that uses the device.
- Allow the HID permission. Start the connection in Rabby, click Allow and authorise your Ledger in the browser pop-up.
- Check cable and port. Use a data cable plugged straight into the computer, and try another port if nothing happens.
- Update the device. Update the Ledger firmware and Ethereum app in Ledger Wallet, then close it again.
- Enable blind signing only if needed. If a dapp transaction is refused, enable blind signing in the Ethereum app settings for that transaction, then consider turning it off.
- Reconnect or switch browser. Unplug, reopen Rabby and reconnect from the beginning. If it still fails, try Brave or Edge.
Rabby talks to a Ledger over USB through the browser's WebHID feature. That connection breaks for a handful of predictable reasons. This page explains the messages Rabby shows and what to do about each, then covers other hardware wallets. For first-time setup, read how to use Ledger with Rabby.
Your Ledger's 24 words are never needed to connect it to Rabby. If any site, pop-up or "support agent" asks you to type them, it is a scam.
What Rabby's Ledger messages mean
These strings come from the English text files in Rabby's extension source code (v0.94.13, October 2026).
| Message | What it means | What to do |
|---|---|---|
Please plug in and unlock your Ledger, open Ethereum on it | Rabby cannot reach the Ethereum app | Connect the cable, enter your PIN, open the Ethereum app on the device |
Your ledger is not connected | The USB link dropped or was never allowed | Reconnect, then reconnect from the beginning in Rabby |
Please install the Ethereum app on your Ledger device. | The Ethereum app is missing | Install it with Ledger Wallet (formerly Ledger Live), then close that app |
You have denied the request to open the Ethereum app. | The open-app prompt was rejected on the device | Try again and approve on the Ledger |
Failed to close the running app on your Ledger device. | Another app is open on the Ledger | Exit that app on the device and open Ethereum yourself |
Please update the firmware and Ethereum App on your Ledger | Firmware or app too old for this request | Update both in Ledger Wallet |
Transaction is rejected on your Ledger | You (or a timeout) rejected it on the device | Start the transaction again and approve on the device |
The checklist, in order
1. One Ledger, unlocked, Ethereum app open
Rabby's own connection guide lists three steps: plug in a single Ledger, enter the PIN, open the Ethereum app. The Ledger screen should show the Ethereum app as ready, not the dashboard. Ledgers lock after a period of inactivity, so unlock again if you stepped away.
2. Close Ledger Wallet
Only one program can use the Ledger's USB connection at a time. If Ledger's desktop app (renamed from Ledger Live to Ledger Wallet in October 2025) is open, Rabby often cannot reach the device. Quit it completely, including from the system tray or menu bar. The same goes for other wallets that are talking to the Ledger.
3. Allow the HID permission
The first time you connect, Rabby asks for permission to Connect to an HID device and tells you to click Allow and authorise your Ledger in the browser pop-up that follows. If you dismissed that pop-up, start the connection again from Rabby. You can also check your browser's site settings for HID devices and remove a stale entry for the Rabby extension so it asks again.
4. Cable, port and hub
Use a data cable (some cheap cables only charge), plug straight into the computer rather than a hub, and try another port.
5. Update firmware and the Ethereum app
Open Ledger Wallet, update the device firmware and the Ethereum app, then close Ledger Wallet again. This also matters for security: Ledger patched Ethereum app flaws in August 2026 that could make the device sign something other than what it displayed (security press, August 2026).
6. Blind signing and contract data
Some dapp transactions and signatures cannot be fully decoded on the Ledger screen. In that case the Ethereum app may refuse them until you enable blind signing in the Ethereum app's settings on the device. Rabby links to Ledger's own blind signing tutorial when this is needed. Only enable it for the transaction you understand (Rabby's simulation shows what it will do), and consider turning it off afterwards.
7. Reconnect from the beginning
Rabby's connection screen suggests reconnecting from the beginning when it does not work. Unplug the Ledger, close and reopen the Rabby window, and go through the connect flow again.
8. Try another browser
Rabby says Ledger is not compatible with Firefox, so use a Chromium browser. In June 2026 one user reported on Reddit that their Ledger stopped connecting to Rabby in Chrome only, while it still worked in other browsers; Rabby support reportedly suggested contacting Chrome support, and neither Rabby nor Ledger confirmed a bug (CoinSpectator repost, 28 June 2026). If Chrome fails, test Brave or Edge with the same Ledger. Because the keys are on the device, nothing needs to be moved.
Other hardware wallets
GridPlus Lattice1. GridPlus documents two Rabby errors: Unable to connect to Hardware Wallet. Please try to re-connect and Failed to get accounts. Please forget the device and try again. Make sure you do not have a locked SafeCard inserted. Its fixes: make sure both the computer and the Lattice are online, update the Lattice firmware and Rabby, unlock the SafeCard, check the device ID and password, and if needed remove the Rabby permission on the Lattice and the linked accounts in Rabby before reconnecting (GridPlus docs, 2026).
BitBox02. BitBox's support pages say to install and run the latest BitBoxBridge, fully close the BitBoxApp, and temporarily disable other wallet extensions. You can check that the bridge is running by opening 127.0.0.1:8178 in a new tab, which should show its version. If signing fails, for example on OpenSea, update the firmware in the BitBoxApp (BitBox support, 2026).
OneKey and Trezor. Rabby's guide asks you to install OneKey Bridge for OneKey. Trezor connects through Trezor Connect; keep the device unlocked and update Rabby, since Rabby fixed Trezor connections under Chrome's newer extension format in August 2026 (Rabby GitHub). More in Rabby with Trezor and Rabby hardware wallets.
Frequently asked questions
Why does Rabby say my Ledger is not connected when it is plugged in?
Usually the Ledger is locked, the Ethereum app is not open, or Ledger Wallet is holding the USB connection. Unlock it, open Ethereum, quit Ledger Wallet and reconnect.
Do I need to enter my Ledger recovery phrase in Rabby?
No. Never. Rabby reads only your public addresses from the device and asks it to sign. Anyone asking for the 24 words is a scammer.
Does Rabby work with Ledger on Firefox?
No. Rabby's own text says Ledger is not compatible with Firefox, and there is no official Rabby Firefox add-on. Use Chrome, Brave or Edge.
Is it safe to turn on blind signing?
It lets the Ledger sign data it cannot show in full, so you rely on Rabby's simulation. Use it only for transactions you understand and consider switching it off afterwards.
Will reconnecting my Ledger change my addresses?
No. The addresses come from the device. Pick the same derivation path (for example Ledger Live or BIP44) when you add them again and the same accounts appear.