Bohdan Triapitsyn
75c90d955c
Add a new tunnels page with verified, up-to-date CLI examples Remove deprecated `--daemon` usage and clarify QR/password behavior Add docs validation tooling and docs-source workflow for packaging and sync
31 lines
774 B
Plaintext
31 lines
774 B
Plaintext
---
|
|
title: Troubleshooting
|
|
description: Common setup and runtime issues with quick fixes.
|
|
---
|
|
|
|
# Troubleshooting
|
|
|
|
## OpenChamber command exits or fails to start
|
|
|
|
- confirm Node.js `>=20`
|
|
- 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
|
|
|
|
## VS Code extension does not connect
|
|
|
|
- confirm OpenChamber server is running
|
|
- verify extension is updated
|
|
- reload VS Code window and retry connection
|