Troubleshooting

The quick fixes for the things people hit most often. If none of these help, contact support and we'll dig in with you.

Nothing appears on the projector

Open Settings → Display and confirm the right monitor is selected under Outputs for the role you're using (Front of house, Stage display, or Broadcast), then click Open.
Click the output toggle (projector icon) in the top bar to open the output window. If you haven't picked a display yet, Verse sends you to Settings to choose one.
Check the Live Display panel isn't Frozen :a frozen output ignores new cues.

See Presentation & output displays for the full flow.

The transcript isn't picking anything up

Press Ctrl/Cmd+R to start transcribing, and make sure your microphone is selected and allowed by the operating system.
On macOS, grant Verse microphone permission in System Settings → Privacy & Security → Microphone.
If you're offline, confirm Whisper is in use — turn on Offline mode under Settings → Audio (the Fast transcription (online) path under Settings → AI needs a connection).

Verses aren't being detected

Detection needs a working transcript first — see above.
Open Settings → AI and check the detector is enabled and the thresholds aren't set too high. Lower them if real references are being missed.
Running local AI? Confirm the Ollama daemon status pill is green and a model is installed. See Local AI with Ollama.

A translation is missing

Open the Bible Store and install the translation you need. Only installed translations appear in the Scripture tab, the Library, and the primary-translation picker.

Activation problems

Re-check the license key under Settings → License, then use Re-activate this device.
If the key is exhausted, free a seat by deactivating an old device in the portal.
Expired or invalid? Manage subscription from the License tab.

Linux: the app won't launch (chrome-sandbox / SUID sandbox error)

On Ubuntu 24.04 you may see a fatal error like:

The SUID sandbox helper binary was found, but is not configured correctly ...
/opt/Verse/chrome-sandbox is owned by root and has mode 4755.

Use the .deb (recommended). sudo apt install ./Verse-x.y.z-amd64.deb installs Verse to /opt/Verse and sets up the Chromium sandbox correctly, so it launches without any further tweaks. Already installed a broken build? Reinstall the latest .deb — the installer now fixes the sandbox permissions on setup.
AppImage on Ubuntu 24.04. First install the FUSE 2 compat library: sudo apt install libfuse2t64. The AppImage's sandbox helper can't be made setuid on its read-only mount, so also enable the user-namespace sandbox:
```
echo 'kernel.apparmor_restrict_unprivileged_userns=0' | sudo tee /etc/sysctl.d/60-userns.conf
sudo sysctl --system
```
Then run the AppImage. As a last resort, ./Verse-x.y.z.AppImage --no-sandbox launches but disables the Chromium sandbox — use only to confirm the app otherwise works, not day to day.
Don't run Verse as root/sudo — Chromium refuses to start as root without --no-sandbox.