2026-03-15 03:30:35 +02:00
|
|
|
---
|
|
|
|
|
title: Troubleshooting
|
|
|
|
|
description: Common setup and runtime issues with quick fixes.
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Troubleshooting
|
|
|
|
|
|
2026-05-23 02:43:34 +03:00
|
|
|
Hit a snag? Find the symptom below and try the fix.
|
|
|
|
|
|
2026-03-15 03:30:35 +02:00
|
|
|
## OpenChamber command exits or fails to start
|
|
|
|
|
|
2026-06-10 17:37:19 +03:00
|
|
|
- confirm Node.js `>=22`
|
2026-03-15 03:30:35 +02:00
|
|
|
- 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
|
|
|
|
|
|
2026-05-23 02:43:34 +03:00
|
|
|
See [Tunnels](/tunnels/) for the full setup, and [Reverse Proxy](/reverse-proxy/) if you run one.
|
|
|
|
|
|
2026-03-15 03:30:35 +02:00
|
|
|
## VS Code extension does not connect
|
|
|
|
|
|
|
|
|
|
- confirm OpenChamber server is running
|
|
|
|
|
- verify extension is updated
|
|
|
|
|
- reload VS Code window and retry connection
|
2026-05-23 02:43:34 +03:00
|
|
|
|
|
|
|
|
## Related
|
|
|
|
|
|
|
|
|
|
- [Quickstart](/quickstart/)
|
|
|
|
|
- [Tunnels](/tunnels/)
|
|
|
|
|
- [Reverse Proxy](/reverse-proxy/)
|
