Bohdan Triapitsyn
7ea974d89b
- new Connect a Device page: one-time QR pairing, transport choices, device management - new Private Relay page: E2EE guarantees, demand-driven lifecycle, relay vs tunnel - rewrite mobile page around the native iOS/Android apps (TestFlight + APK) - update remote-instances, security, tunnels, and remote-access troubleshooting to point at the new pairing flow - translate everything across all 8 locales and update the sidebar
48 lines
2.2 KiB
Plaintext
48 lines
2.2 KiB
Plaintext
---
|
|
title: Remote Access
|
|
description: Fix tunnels, remote instances, and reaching OpenChamber from another device.
|
|
---
|
|
|
|
# Remote Access
|
|
|
|
When you can't reach OpenChamber from your phone or another machine, the fix depends on how you're connecting.
|
|
|
|
## Check the basics first
|
|
|
|
- open `http://localhost:3000` on the same computer first — if that fails, it's not a remote problem; see [OpenCode connection](/troubleshooting/opencode-connection/)
|
|
- confirm the server is running with `openchamber status`
|
|
|
|
## Paired device won't connect
|
|
|
|
- the QR code / pairing link is **single-use** — if it was already scanned (or expired), create a new one from **Add a device**
|
|
- if the device was paired with **Home network only**, it can't connect from outside that network — pair it again with **Anywhere**
|
|
- for **Anywhere** pairing, check **Settings → Remote Instances → OpenChamber Relay** on the server: it should say **Connected**; if not, disable and re-enable it
|
|
- if a device was **revoked**, its token is gone for good — pair it again with a new QR code
|
|
|
|
See [Connect a Device](/connect-devices/) and [Private Relay](/private-relay/) for how these connections work.
|
|
|
|
## Tunnel link doesn't work
|
|
|
|
- run `openchamber tunnel status --all`
|
|
- restart the tunnel from the same instance and port
|
|
- regenerate the connect link if the previous one was already used
|
|
|
|
See [Tunnels](/tunnels/) for the full setup.
|
|
|
|
## Remote instance won't connect (desktop)
|
|
|
|
When a [remote instance](/remote-instances/) stalls, OpenChamber names the step that failed:
|
|
|
|
- **auth** — your SSH or UI password was rejected; re-enter it
|
|
- **install / start** — OpenChamber couldn't set up or start the server on the remote machine; check that machine's requirements
|
|
- **forwarding** — the connection is up but the port isn't reaching you; try a different local port
|
|
|
|
## Behind your own server
|
|
|
|
If you put OpenChamber behind a reverse proxy and it loads oddly or won't connect, see [Reverse Proxy](/reverse-proxy/).
|
|
|
|
## Related
|
|
|
|
- [Connect a Device](/connect-devices/) · [Private Relay](/private-relay/) · [Tunnels](/tunnels/) · [Remote Instances](/remote-instances/) · [Reverse Proxy](/reverse-proxy/)
|
|
- [Security](/security/) — protect the UI before exposing it
|