From 1a05d8ca1a5ab8d8562eb576bfd473459dcc8ea3 Mon Sep 17 00:00:00 2001 From: Julius Marminge Date: Fri, 10 Apr 2026 00:43:38 -0700 Subject: [PATCH] Document remote server network access setup (#1872) --- REMOTE.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/REMOTE.md b/REMOTE.md index f1748387a1fada6e3033cc0ae80a2ec954078ab6..30dc562792f7f52deeabd9d64aa53a042149530b 100644 --- a/REMOTE.md +++ b/REMOTE.md @@ -12,7 +12,22 @@ That gives you: - transport security at the network layer - less exposure than opening the server to the public internet -## Headless Server Flow +## Enabling Network Access + +There are two ways to expose your server for remote connections: from the desktop app or from the CLI. + +### Option 1: Desktop App + +If you are already running the desktop app and want to make it reachable from other devices: + +1. Open **Settings** → **Connections**. +2. Under **Manage Local Backend**, toggle **Network access** on. This will restart the app and run the backend on all network interfaces. +3. The settings panel will show the address the server is reachable at (e.g. `http://192.168.x.y:3773`). +4. Use **Create Link** to generate a pairing link you can share with another device. + +### Option 2: Headless Server (CLI) + +Use this when you want to run the server without a GUI, for example on a remote machine over SSH. Run the server with `t3 serve`. -- 2.54.0