# fix\(server\): keep the managed tunnel across remote update restarts · gitcafe/t3code

[View on GitCafe](https://git.cafe/gitcafe/t3code/commit/808d6853555c8b57f414a06e0a79eb1b9e192ef5)

Repository: [gitcafe/t3code](https://git.cafe/gitcafe/t3code)

Visibility: public

Requested revision: 808d6853555c8b57f414a06e0a79eb1b9e192ef5

Requested commit: 808d6853555c8b57f414a06e0a79eb1b9e192ef5

Commit: 808d6853555c8b57f414a06e0a79eb1b9e192ef5

Tree: 3ee03f5422092b66f9ef3c4b8dbc2a537be7ee3d

Author: Theo Browne

Committer: Theo Browne

## Message

```
fix(server): keep the managed tunnel across remote update restarts

Measured on a live update: the server was back in ~9s but stayed
unreachable for ~96s, because releasing the tunnel on shutdown forces
the replacement tunnel's hostname route through 1-2 minutes of edge
propagation. An update handoff always brings a server right back
(new version or rollback), so the tunnel is never orphaned; skip the
release when the launcher state file records a pending update. The
next boot respawns the connector from the stored config against the
same tunnel and is reachable as soon as it connects.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

```

## Parents

- [80720ad592dc68c29677444fd7b6abb97b82c03e](https://git.cafe/gitcafe/t3code/commit/80720ad592dc68c29677444fd7b6abb97b82c03e?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/t3code/tree/808d6853555c8b57f414a06e0a79eb1b9e192ef5?format=markdown)