BitBox not connecting to computer

Table of Contents

Quick checks Check if the operating system detects the BitBox macOS Windows Linux Fix USB permissions on Linux Further solutions Still having trouble?

If your BitBox does not connect to your computer, start with these simple fixes.

Quick checks

First, check your setup and connections. Most issues are solved here.

Reboot your computer: A simple restart can fix many temporary connection issues.
Try a different USB cable: If you have another compatible USB cable, try using it. The original cable could be damaged.
Remove screen protector: If the protective sticker is still on the BitBox screen, please remove it.
Check orientation: Connect the BitBox with its screen facing up.
Use a direct connection: Plug your BitBox directly into a USB port on your computer. Avoid USB hubs, docking stations, or extension cables.
Try different USB ports: Test other USB ports on your computer to rule out a faulty port.
Test on another device: If possible, connect your BitBox to a different device, like another computer or an Android smartphone. This helps identify if the issue is with your computer or the BitBox.

Check if the operating system detects the BitBox

Even if the BitBoxApp doesn't see your device, your computer might.

macOS

Open the Terminal app.
Run this command:

ioreg -p IOUSB -l -w 0 | grep "BitBox"

If your device is detected, you will see an entry containing "BitBox".

Windows

Open Device Manager.
Expand the Universal Serial Bus controllers section.
Look for USB Composite Device.
Right-click it, select Properties > Details tab.
Choose Hardware Ids from the dropdown menu.
If the Hardware Ids include VID_03EB and PID_2403, Windows detects your BitBox.

Linux

Open a Terminal.
Run this command:

lsusb

Look for an entry containing "BitBox" or 03eb:2403.

Fix USB permissions on Linux

If lsusb detects the BitBox but the BitBoxApp does not, you may need to fix the USB permissions.

Another way is to download and run the udev rules script from the official Shift Crypto GitHub repository.

Open a Terminal.
Run the following commands one by one:

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/null

printf "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/null

sudo udevadm control --reload

sudo udevadm trigger

If issues persist after setting the rules, add your user to the plugdev group. This command usually works automatically (replace $USER with your actual username if needed):

sudo usermod -aG plugdev $USER

Afterward, unplug and reconnect your BitBox. A reboot may be necessary.

Further solutions

If the problem continues, try these steps:

Update conflicting software: Applications like Citrix Workspace can interfere with USB devices. Ensure they are fully updated.
Update USB drivers (Windows): Update your USB drivers through the Device Manager.
Temporarily disable security software: Your antivirus or firewall might block new USB devices. Disable them briefly to test the connection, and re-enable them immediately after.
Reinstall the BitBoxApp: If the OS detects the BitBox but the app doesn't, the app installation may be corrupt. Try reinstalling the BitBoxApp from the official website.

Still having trouble?

If you have tried all these steps, please contact BitBox support.

Include the following information to get a faster solution:

Your computer model and operating system version.
Your BitBoxApp version.
A description of the steps you have already tried.
The BitBoxApp log files. You can learn how to get them by following this guide on how to get the BitBoxApp log files.