Troubleshooting

Work from scope to signal.

Most TvRMM troubleshooting starts by confirming tenant visibility, endpoint identity, platform lane, and whether the action is owned by a direct agent, a host, or an appliance-native workflow.

Endpoint missing after install

Generate a fresh portal bootstrap, confirm the selected organization, check outbound connectivity to the agent endpoint, and verify the agent service is running on the target host.

Action button disabled

Check your effective role and the operating-as selector. Actions such as scripts, terminal, patch install, reboot, homelab controls, user management, and deletion require more than viewer access.

Guest row is host-observed

A Proxmox VE or Unraid guest row may be inventory observed by the host, not directly managed by an in-guest agent. Install and link a real in-guest agent when direct endpoint behavior is required.

Patch scan differs by OS

Patch behavior depends on package manager, repositories, entitlement, appliance policy, and lab evidence. Do not assume apt, dnf, yum, zypper, pacman, apk, PVE, and Unraid behave the same.

Platform kind looks wrong

Check whether the endpoint is a direct agent, Proxmox VE host, Unraid host, host-observed guest, linked guest, or staged evidence platform. Some collectors update platform kind after the next audit.

Deleted endpoint still exists

TvRMM hides deleted endpoints from active views, queues uninstall, revokes certificates, and lets cleanup complete when the endpoint or host reports the uninstall result.

Evidence to collect

Need support?

Use the contact form for product fit or support questions. Do not send secrets, private keys, or enrollment tokens through the form.

Check support lane

When behavior depends on platform coverage, review the lane language first.