Solve problems

First open the Web dashboard with the same account used by the installer. Check the latest report time.

Missing or old on Web too: check the sending tool or collector below.
Current on Web but missing in Desktop or iPhone: check that viewer's sign-in and display choices. Reinstalling the collector is not the first step.
Present with a missing measurement: check whether the tool or machine supports that value. — does not mean zero.

After a fix, start another coding task or leave the collector running. Confirm that the Web report time advances, then check the viewer again.

Nothing appears

Problem	Action
A coding account does not appear	Restart the tool and start a coding session. In Codex, trust the VibeMon hooks in `/hooks`.
A server does not appear	For a normal user installation, run `systemctl --user status vibemon-collector --no-pager` on the server. For root installation, use `sudo systemctl status vibemon-collector --no-pager`. See collector diagnostics.
A cluster does not appear	Confirm `kubectl config current-context`, then run `kubectl -n vibemon get pods` and `kubectl -n vibemon logs deployment/vibemon-collector --tail=30`. Check Ready and the Web report time, not only Running.
An item is missing from the dashboard	Clear search and filters. In Overview → Customize view, select the item. Use View all to see beyond the overview preview.
CPU and memory of a cluster are Unavailable	Run `kubectl top nodes`. If it fails, ask the administrator to check metrics-server and permissions; if nodes are missing, fix that before expecting a complete cluster total.

Data stopped

Problem	Action
A computer stopped sending data	If its token was deleted, sign in again. See Sign in again.
A server stops after you log out	Run `sudo loginctl enable-linger $USER` on the server.
Connection interrupted	Check your network. The dashboard tries again automatically and keeps the last values.
Stale	The resource sent no report for 2 minutes. Check that the computer and the collector run.

If collector logs show HTTP 401, reconnect the sender. For 403, it needs Write permission. Exit code 2 means the collector stopped on a configuration rejection; correct the token, Web address, machine clock, or reported definition before restarting. For temporary network errors or 429, it retries automatically; repeated reinstalls will not fix the cause.

Use the same operating-system user and, for collectors, the original --name and kubectl context. Append --name "Your original name" below if you set one during installation. Run only the command for the affected sender:

# Coding tools
curl -fsSL https://vibemon.io/install/install.py | python3 - --all --login
# Linux server or DGX Spark
curl -fsSL https://vibemon.io/install/install.py | python3 - --collector --login
# Kubernetes cluster of the current kubectl context
curl -fsSL https://vibemon.io/install/install.py | python3 - --kubernetes --login

For coding tools on Windows PowerShell:

& ([scriptblock]::Create((irm https://vibemon.io/install/install.ps1))) --all --login

Approve the new code on vibemon.io/device with the intended account. A saved VIBEMON_WRITE_TOKEN environment variable takes precedence over --login; remove that override from the launching environment if you want browser sign-in. Restart coding tools after reconnecting, then verify a new Web report. After the replacement works, delete the obsolete token in Account & tokens.

Desktop App

Problem	Action
The App shows no cloud data but Web does	Check the same account in Settings → Connections, then Overview → Customize view. Reconnect if the App reports an authentication error.
Local activity works but Web is empty	Open Settings → Integrations → Send activity to Web and sign in there. The viewing connection is separate.
A widget shows Open VibeMon	Start the App.
A widget shows Restart VibeMon	Quit and reopen the App.

Installer

Problem	Action
Windows opens the Microsoft Store	Install Python from python.org, or turn off the App execution aliases for Python in Windows settings.
The installer stops with a verification error	Wait a few minutes and run it again. Do not disable the integrity check. If it still fails, send the message to support.
The code expired	Run the installer again. A code is valid for 10 minutes.

Get help