| Issue Type | Primary Cause | Quick Fix |
|---|---|---|
| Permissions | OS-level Bluetooth access blocked | Grant Chrome permission in System Settings |
| Experimental Feature | Web Bluetooth API disabled | Enable #enable-web-bluetooth in Chrome Flags |
| Driver Conflict | Outdated Bluetooth stack | Update drivers via Device Manager |
| Device State | Device already paired elsewhere | Unpair and restart discovery mode |
What is Chrome Bluetooth Connection Refused?
The “Chrome Bluetooth connection refused” error occurs when the browser’s Web Bluetooth API fails to establish a handshake with a hardware device. This typically happens during the pairing process in web applications.
This error is a security or configuration hurdle. Chrome requires specific permissions and experimental flags to be active before it can communicate with low-energy (BLE) devices.
When the connection is refused, the browser effectively blocks the communication port. This protects users from unauthorized hardware access but prevents legitimate developers and tools from functioning.
Step-by-Step Solutions
1. Enable Web Bluetooth Flags
Chrome often hides Bluetooth capabilities behind experimental flags. You must manually enable these to allow the API to function.
# Paste this into your Chrome address bar:
chrome://flags/#enable-web-bluetooth
Set the “Web Bluetooth” flag to **Enabled** and click the **Relaunch** button at the bottom of the window to apply changes.
2. Check OS Privacy Settings
Modern operating systems like macOS and Windows 11 require you to grant specific apps permission to use Bluetooth.
On macOS, go to **System Settings > Privacy & Security > Bluetooth** and ensure Google Chrome is toggled on. On Windows, ensure “Bluetooth” is enabled under **Privacy & security > Radios**.
3. Clear Bluetooth Cache and Restart Services
Sometimes the internal Bluetooth stack becomes unresponsive. Restarting the service can force a clean handshake.
On Windows, you can restart the service using the command prompt as Administrator:
net stop bthserv
net start bthserv
4. Reset Chrome Browser Settings
If flags and permissions are correct, a corrupted browser profile might be the cause. Resetting Chrome’s settings can resolve underlying conflicts.
Go to **Settings > Reset settings > Restore settings to their original defaults**. This will not delete your bookmarks but will disable extensions that might be interfering with the Bluetooth hardware.
5. Verify Device Pairing Mode
Ensure the hardware device is not currently connected to a smartphone or another computer. Bluetooth LE devices often refuse new connections if an active session is already established.
Put your device back into “Discovery Mode” (usually by holding a physical button) before clicking “Pair” in the Chrome browser popup.