---
title: Troubleshooting
description: Common setup and runtime issues with quick fixes.
---

# Troubleshooting

Hit a snag? Find the symptom below and try the fix.

## OpenChamber command exits or fails to start

- confirm Node.js `>=22`
- run `openchamber --version`
- reinstall latest CLI if needed

## Web UI is not reachable

- check server logs with `openchamber logs`
- verify active port (default `3000`)
- open `http://localhost:3000` directly first before testing tunnel links

## Remote/tunnel link does not work

- run `openchamber tunnel status --all`
- restart tunnel from the same instance/port
- regenerate connect link if previous token was already used

See [Tunnels](/tunnels/) for the full setup, and [Reverse Proxy](/reverse-proxy/) if you run one.

## VS Code extension does not connect

- confirm OpenChamber server is running
- verify extension is updated
- reload VS Code window and retry connection

## Related

- [Quickstart](/quickstart/)
- [Tunnels](/tunnels/)
- [Reverse Proxy](/reverse-proxy/)