Skip to content

Commit df70f50

Browse files
b2bvicVictor Romoclaude
authored
docs: scope managed-policy LAN note to old background services (#30900)
Co-authored-by: Victor Romo <[email protected]> Co-authored-by: Claude Opus 5.5 <[email protected]>
1 parent 7f6f47b commit df70f50

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

‎docs/user/managed-policy.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -224,8 +224,10 @@ desktop app, keep `desktop` in the list, or the app cannot start.
224224

225225
Without `remote`, the server listens only on a loopback address, creates no pairing links, and
226226
signs out devices that paired earlier. It does not start with a host other than a loopback
227-
address or `localhost`. The [background service](./background-service.md) listens on private
228-
networks by default, so set `T3CODE_HOST=127.0.0.1` in its `service.env`. The desktop app starts
227+
address or `localhost`. A [background service](./background-service.md) installed before
228+
`T3CODE_LAN` existed keeps private-network access, so without `remote` it refuses to start.
229+
Run `t3 up --no-lan` when its `service.env` sets no `T3CODE_HOST`, or set
230+
`T3CODE_HOST=127.0.0.1` in `service.env`, then run `t3 service restart`. The desktop app starts
229231
with network access and Tailscale Serve off, whatever the user chose. That also turns off
230232
T3 Connect. To keep other remote access but turn off T3 Connect alone, set `"connect": false`.
231233

0 commit comments

Comments
 (0)