Manual for Bouncer 0.5.7. Chapters state version and distribution limits. Source cdd3b59, site build 20 November 2026. Your server or app may run an earlier version.
On this page
Troubleshooting
Problems you can fix from the app side, by what you see. Pairing problems are on Pair the app with your server, and approval refusals on Answer requests.
If nothing here helps, ask your administrator, or see Support.
Can't reach the server
"Can't reach your Bouncer server", or Offline under Server in Settings.
From 0.5.7, a brief "Reconnecting…" notice can appear at the bottom of the screen when you unlock your device or return to Bouncer, while the connection comes back. If the server still can't be reached after a few seconds, the app shows "Can't reach your Bouncer server".
- Check the device is connected to a network that reaches your Bouncer server.
- If your organisation uses a VPN for Bouncer, check it's connected on this device.
- Tap Try again.
Nothing is approved or changed while the app is offline. Requests wait on the server for their time to answer, so you can still answer them once you're back. Settings shows when the server was last reached.
The server is running but can't serve
These messages mean nothing is wrong with your device. Tell your administrator (whoever runs your Bouncer server). There's nothing to fix on the phone or PC, and no need to pair again.
| The app says | What's wrong |
|---|---|
| "Your Bouncer server returned an error" | From 0.5.7: the server answered with an error. Tell your administrator what you were doing. |
| "Your Bouncer server can't reach its database" | From 0.5.7: the server cannot reach PostgreSQL. Your administrator must fix it. |
| "Your Bouncer server's vault is sealed" | The vault (OpenBao, where the server keeps credentials) is sealed, usually after a restart. Your administrator must unseal it |
| "Your Bouncer server can't reach its vault" | The vault is stopped or out of the server's reach |
| "Your Bouncer server can't sign in to its vault" | The vault refused the server's own sign-in |
| "Your Bouncer server isn't answering" | Its address answers, but the server behind it doesn't: it's stopped or restarting |
Tap Try again once your administrator says it's fixed. Their side is in When Bouncer is unavailable.
No notifications
On Android
- Open Bouncer's Settings, and under Notifications tap Notification settings. If it says notifications are turned off for Bouncer, turn them on in Android settings.
- Android 13 and later ask for permission to show notifications. If you chose Not now when pairing, turn notifications on there.
- Battery savers can delay notifications. If they come late, let Bouncer run unrestricted in Android's battery settings for the app.
- Open Bouncer. Requests always show in the Inbox, notification or not.
If Settings says Push notifications are off in this build, this copy of the app was built without its notification settings. Requests show only when you open the app. Ask for a normal build.
On Windows
- Bouncer must be running. Check for its icon in the notification area (the tray; it may be under the ^ arrow). If it isn't there, start Bouncer Desktop from the Start menu. Windows has no push to a closed Bouncer.
- Check Settings > System > Notifications in Windows: Bouncer and notifications in general must be on, and Do not disturb off.
- While the PC is locked, notifications only say "Access request pending" and "Unlock this PC to see the details".
The phone won't approve or deny
When the phone can't use its approval key, the app says why. Nothing was approved or denied in any of these cases.
| What you see | What to do |
|---|---|
| Your phone is locked | Unlock it, then try again. |
| Android needs a fresh unlock | On Android 12 to 14, some face unlocks and Smart Lock don't count for Bouncer's key. Lock the phone, unlock it with your PIN, pattern, password or fingerprint, then try again. |
| Not confirmed | You cancelled the fingerprint check, or it timed out. Try again. |
| Too many attempts | Wait a moment, or lock the phone and unlock it with your PIN, pattern or password. |
| Bouncer wasn't on screen | Keep Bouncer open while you confirm. |
| Fingerprint check isn't available | Check a fingerprint is set up in Android settings. |
| Another confirmation is open | Finish or cancel the other fingerprint check. |
| This phone's key stopped working | Your fingerprints changed, so Android retired the key. Pair again. |
| This phone couldn't use its key | Unlock the phone and try again. If it keeps happening, pair again. |
Windows Hello problems
| What you see | What to do |
|---|---|
| "Windows Hello was cancelled. Nothing changed." | Try again. If you answered No to "Let Bouncer Desktop create and use passkeys?", turn Bouncer Desktop on under Settings > Privacy & security > Passkeys > Let apps create and use passkeys. |
| "Windows Hello couldn't make a passkey for Bouncer Desktop." | Set up a Windows Hello PIN under Settings > Accounts > Sign-in options, and check the passkeys setting above. |
| "Windows Hello approvals need a PC with a security chip (TPM)." | This PC can't approve. Approve on another paired device. |
| "Windows Hello didn't sign. Nothing was sent." | Try again. |
A request disappeared
Requests wait for a limited time. If nobody answers in time, a request expires and nothing is granted. It also leaves your inbox when someone answers it on another device, or the requester cancels it. Grants, then History, shows what happened to it.
The camera doesn't open
Allow camera access for Bouncer in Android settings, or tap Enter the code instead. Bouncer uses the camera only to read the pairing QR code. The Windows app doesn't use a camera.
Windows: a plugin DLL is missing
You started the portable ZIP's Bouncer.exe from inside the ZIP, or copied
it on its own. Extract the whole ZIP with Extract All and run
Bouncer.exe from the extracted folder, with its DLLs and data folder
beside it.
Windows: "Windows protected your PC"
The portable ZIP isn't signed, so SmartScreen doesn't recognise it. Choose More info, then Run anyway, if the file came from your organisation. The MSIX installer avoids this, once its certificate is trusted.
The app looks wrong after an update
Check the version in Settings under About. If Bouncer starts on the pairing screen after an update, the old app was removed before the new one was installed, so the pairing was lost. Pair again, and ask your administrator to revoke the old pairing.