Doctor & troubleshooting

When something isn't routing or a server won't start, Doctor tells you what's wrong and how to fix it - in the app or from the CLI.

$ rig doctor

What it checks

• DNS - the embedded server on port 5300 is up and resolving *.rig.
• Proxy - the reverse proxy is bound and listening.
• Helper - the privileged daemon owns port 80.
• Resolver file - /etc/resolver/rig exists and points at the DNS server.
• Ports - no conflicts on assigned project ports.

Common issues

project.rig doesn't resolve

Routing probably isn't enabled yet. Open Doctor → Enable .rig domains and approve the admin prompt. Doctor also shows the manual sudo command if you prefer to run it yourself. Until then, use the localhost:PORT URL.

Port 80 is in use

Another app (often a different local dev tool) is holding port 80, so .rigrouting can't bind. Rig falls back to localhost URLs automatically. Stop the other service, or keep using localhost.

A server won't start on its port

A previous crash may have left an orphan process holding the port. Free it, then start again:

$ rig free-port 3001
$ rig start acme-storefront

The CLI says Rig isn't running

rig talks to the desktop app over a local socket. If you see APP_NOT_RUNNING (exit code 4), launch the Rig app, then retry.