Chapter 13

Troubleshooting

Common symptoms, their causes and the steps that resolve them.

Common situations

SymptomConfirmed behaviourWhat to check
Tab dot is yellow connection-suspect: keepalive reports trouble Network path and keepalive interval/retry settings; reconnect the tab
Tab dot is red connection-closed: the session ended Reconnect reuses the tab; a new session_id is assigned
No containers listed locally probe_local_docker tries docker, then podman, and separates “not installed” from “daemon not running” Read which of the two states the probe reports before changing anything
Remote Git command hangs Remote Git runs with GIT_TERMINAL_PROMPT=0, so no interactive prompt is possible Ensure credentials are already available to the non-interactive shell
Recordings are missing Recording is off by default; WROLP_RECORDING=1 forces it on Check the setting and the environment variable, then look under recordings/
AI keys stop working after moving data vault.key is machine-bound and only moves if you migrate it explicitly Re-run migration with the vault key, or re-enter the API keys
A shortcut cannot be assigned Tab, Enter, Ctrl+C/V/X/Z/D/W are reserved Choose another combination
Unknown Git state in the panel Status comes from porcelain v2 and diff is capped at 2 MB A very large change set is truncated by design
Updater does not work The manifest comes from releases/latest/download/latest.json and installers are verified with pubkey Check network access and that the release includes latest.json

Platform and packaging problems

Database size

Recordings live as files and only their index is stored in SQLite, so wrolp.db should not grow with recording length. If it has grown for other reasons, settings show the reclaimable space and offer Compact now (VACUUM).

Reporting a problem

Report bugs and feature requests through the issue templates on github.com/wrolp/wrolp/issues. Include the application version (Settings → About), the affected host or protocol, and the exact steps that reproduce the problem.