How to get help
Most issues resolve from a guide or the FAQ. When they don’t, Support is a real human inbox — not a ticket void. This page is the shortest path to an answer.
1. Check docs and FAQ
- Browse the help docs hub.
- Skim the troubleshooting FAQ.
- See if it already shipped in the changelog.
2. Try the in-app fix first
- Ports — reclaim from the project or ⌘K → reclaim.
- Setup diagnose — Settings / Setup for Docker, DB, and common missing tools.
- Restart the process — then check the unified log pane for the real exit reason.
3. Open Support
Go to help.userig.app. From the Mac app: Help → Contact support…. We use tickets to improve these docs — if something was missing, tell us which guide should have answered it.
What to include (checklist)
- Rig version (About Rig, or Settings → Updates)
- Mac model + macOS version (Apple menu → About This Mac)
- Apple Silicon or Intel
- Project type (Node, Laravel/Valet, Docker Compose, etc.)
- What you expected vs what happened
- Screenshot or a short log clip (last ~30 lines is usually enough)
- Whether you’re signed into a cloud account (yes/no)
What we can help with
- Install, Gatekeeper, and updates
- Process start/stop, ports, logs, MCP linking
- Live Link / LAN share behaviour
- Cloud sync and Continuity (without ever asking for your recovery key in chat)
What we don’t cover yet
- Windows / Linux desktop builds (Mac-only for now)
- Writing your application code or designing your schema
- Hosting or production deploys — Rig is local control, not a PaaS
Prefer email? Use Support first so threads stay searchable. Account and billing questions can also start from your cloud account.