Troubleshooting
Diagnose login, Group, Federation, server, sync, and file-size errors.
Route not found when joining a Group
The App and Vibecape Server are running incompatible versions, or the App points to an older server process. Upgrade both, restart the server, and confirm vibecape server status reports the expected public URL.
Federation is unavailable
The Vibecape Server could not identify the App's Federation token. Check the server's network access to its configured Federation, Bureau Token, and City ID. This is an authentication dependency, not a Git error. Vibecape reports the failure directly and does not hide it behind repeated retries.
The Group immediately shows joined
The current user is already a member—commonly because that user was assigned as Owner when the Group was created. New users who are not members should first see pending.
I cannot create a Space
Only the Group Owner can create Spaces in Phase 1. Editors and Viewers can open existing Spaces. Verify the current account and role in the App's Group settings.
The server occupies my terminal
Use vibecape server start for normal background operation. vibecape server start --foreground intentionally stays attached for debugging or when systemd, Docker, or Dokploy manages the process. Press Ctrl+C to stop a foreground process; use vibecape server stop for a background process.
Push or sync is rejected
Confirm that your membership is still active and your role is Owner or Editor. The server also rejects force pushes, deletion of main, non-main branch updates, and individual blobs larger than 20 MiB.
How do I resolve a sync conflict?
The conflict panel lists real content files. Choose Keep mine or Use remote for each file, or edit conflict markers manually, save, and select Continue sync. Abort sync exits the rebase and preserves the local changes from before syncing.
.downcity/ and .vibecape/ are machine-local runtime state and never require manual merging. Vibecape automatically stops tracking them while preserving the local files.