hstack (local stack)
Troubleshooting
High-signal fixes for common local issues (auth, ports, wrong checkout, unhealthy stacks).
“No machine” / auth required
Most “auth is broken” symptoms are one of:
- you opened the wrong stack URL (browser origin collision)
- the stack did not get seeded auth (non-main stacks)
- the stack is pointed at an unexpected repo checkout
Check:
hstack where
hstack stack info <stack>Fix auth seeding:
hstack auth seed
hstack auth seed --force
hstack stack auth <stack> copy-from dev-auth“This stack is using the wrong checkout”
Check the pinned repo:
hstack stack info <stack>
cat ~/.happier/stacks/<stack>/env | rg HAPPIER_STACK_REPO_DIRRepoint:
hstack stack wt <stack> -- use dev
# or:
hstack stack wt <stack> -- use pr/123-some-prPort collisions
If hstack refuses to start because a pinned port is in use:
- stop the stack:
hstack stack stop <stack> - or unpin ports (then re-run start/dev):
- use
hstack stack edit <stack> --interactive, or hstack stack audit --fix-ports
- use
Stack is unhealthy / can’t reach server
hstack stack doctor <stack>
hstack logs:tailIf you’re using full server (happier-server), verify Docker:
docker ps“I changed something but nothing updates”
In dev mode, prefer running with --restart at least once (so hstack owns the PIDs and can restart safely):
hstack stack dev <stack> -- --restartIf you’re running hstack dev outside stack mode, do:
hstack dev --restart