If your BitBox02 is not connecting to your computer or is not detected by the BitBoxApp, this is usually quick and easy to fix.
This guide walks you step by step through the most common causes—from simple checks to operating system–specific solutions on macOS, Windows, and Linux. Following this guide helps you quickly determine whether the issue is related to your USB connection, software configuration, or operating system.
First, check: Is your app and firmware up to date?
Before starting with troubleshooting, please make sure that:
- you are using the latest version of the BitBoxApp, and
- the firmware on your BitBox is up to date.
Outdated app or firmware versions can prevent the BitBox from being detected correctly, even if it is properly connected.
Quick checks
Always start with these basic steps. In most cases, the issue is resolved here.
-
Try a different USB cable
Faulty USB cables are the most common cause of connection issues—even new ones. If possible, test with another compatible cable. -
Use a direct USB connection
Connect the BitBox02 directly to a USB port on your computer.
Avoid USB hubs, docking stations, or extension cables. -
Switch USB ports
Try a different USB port on your computer. -
Check the orientation
Connect the BitBox02 so that the screen is facing up. -
Restart your computer
A simple reboot can resolve temporary USB or driver issues. -
Test on another device
If possible, connect your BitBox02 to:- another computer, or
- an Android smartphone.
This helps determine whether the issue is related to your computer or the BitBox02 itself.
If the BitBox02 works on another device, the issue is very likely related to your original computer or its configuration.
Additional solutions
If the quick checks did not help, try the following:
-
Update conflicting software
Applications such as Citrix Workspace can interfere with USB device detection. Make sure such software is fully up to date. -
Update USB drivers (Windows)
Open the Device Manager and check for updates for your USB controllers. -
Temporarily disable security software
Antivirus software or firewalls may block new USB devices.
Disable them briefly for testing and re-enable them immediately afterward.
If this resolves the issue, add the BitBoxApp to the allowed list instead of keeping protection disabled. -
Reinstall the BitBoxApp
If your operating system detects the BitBox02 but the BitBoxApp does not, the app installation may be corrupted.
Download and reinstall the BitBoxApp from the official website. -
Remove the screen protection foil
If a protective foil is still attached to the BitBox02 screen, please remove it.
BitBox02 Nova & iOS
- The BitBox02 Nova can experience Bluetooth-specific issues on iOS.
- See this troubleshooting guide: Troubleshooting BitBox02 Nova Bluetooth issues on iOS
Check whether your operating system detects the BitBox
Even if the BitBoxApp does not show your device, your operating system may already recognize it. This helps narrow down the cause.
macOS
- Open the Terminal app.
- Run the following command:
ioreg -p IOUSB -l -w 0 | grep "BitBox" - If macOS detects the device, you will see an entry containing “BitBox”.
Windows
- Open the Device Manager.
- Expand USB controllers.
- Look for USB Composite Device.
- Right-click it and select Properties → Details tab.
- Choose Hardware IDs from the dropdown menu.
If the IDs include VID_03EB and PID_2403, Windows recognizes your BitBox.
Linux
- Open a terminal.
- Run:
lsusb - Look for an entry containing BitBox or
03eb:2403.
If your operating system detects the BitBox, the issue is most likely not a hardware problem, but related to the BitBoxApp or system permissions.
Fix USB permissions on Linux
If lsusb detects the BitBox but the BitBoxApp does not, USB permissions may be missing.
Recommended approach
- Download and run the official udev rules script from the Shift Crypto GitHub repository:
frontends/qt/resources/deb-afterinstall.sh
Alternatively, you can add the rules manually:
printf "SUBSYSTEM==\"usb\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"bitbox_%%n\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\"\n" | sudo tee /etc/udev/rules.d/53-hid-bitbox.rules > /dev/nullprintf "KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", ATTRS{idVendor}==\"03eb\", ATTRS{idProduct}==\"2403\", TAG+=\"uaccess\", TAG+=\"udev-acl\", SYMLINK+=\"bitbox_%%n\"\n" | sudo tee /etc/udev/rules.d/54-hid-bitbox.rules > /dev/nullsudo udevadm control --reload
sudo udevadm triggerIf the issue persists, add your user to the plugdev group:
sudo usermod -aG plugdev $USERDisconnect and reconnect your BitBox afterward. A system reboot may be required.
Only perform these steps if you are comfortable working with Linux system commands.
Still having problems?
If you have completed all steps in this guide, our support team will be happy to help.
Please include the following information so we can assist you efficiently:
- your computer model and operating system version
- the BitBoxApp version you are using
- a short description of what you have already tried
- the BitBoxApp log files
How to export log files:
Locating and exporting BitBoxApp support files
If you reached this point, you have already completed all standard troubleshooting steps. Our support team can now investigate more specifically.
FAQ – Frequently asked questions
Is my BitBox defective if it is not recognized?
In most cases, no. Connection issues are usually caused by cables, USB ports, drivers, permissions, or software conflicts. Hardware defects are rare.
Why does my computer detect the BitBox, but the BitBoxApp does not?
If the operating system detects the BitBox, the issue is very likely related to the BitBoxApp, missing permissions, or blocking software such as antivirus tools.
Can I lose my coins because of connection issues?
No. Your coins are not stored on the BitBox, but on the blockchain. As long as your recovery words are safely backed up, your funds are not at risk.
The BitBox works on an Android device but not on my computer—what does this mean?
This indicates that the BitBox itself is functioning correctly. The issue is almost certainly related to your computer or its software configuration.
When should I contact support?
If you have:
- tried multiple cables and devices,
- confirmed that the operating system does not detect the BitBox, or
- completed all steps in this guide,
please contact support so we can assist you further.