# \[Bug\]: Tailscale Serve failures are only logged as a warning; the server silently stays loopback-only · Issue \#16238 · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/issues/16238)

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

Visibility: public

State: backlog

Priority: 0

## Description

[Discussion and activity](https://git.cafe/pingdotgg/t3code/issues/16238)

---

### Before submitting

- [X] I searched existing issues and did not find a duplicate.
- [X] I included enough detail to reproduce or investigate the problem.

### Area

apps/server

### Steps to reproduce

1. On Linux, as a user who is not the Tailscale operator (or on a tailnet with HTTPS certificates disabled), run `t3 serve --tailscale-serve`.
2. Watch the output and try to reach the server from another tailnet device.

### Expected behavior

When Tailscale Serve was requested and fails, the failure is visible: an error with the reason and a remedy (for example "not the Tailscale operator: run `sudo tailscale set --operator=$USER`"), surfaced in the CLI output, `t3 service status` and Settings → Connections, ideally with retry.

### Actual behavior

The server starts normally, listens on 127.0.0.1 only, and is unreachable from the tailnet. The only trace is a log warning; there is no retry and no user-visible signal.

From the 0.0.45 bundle: `src/server.ts` wraps `ensureTailscaleServe(...)` in `catch_(cause => logWarning("Failed to configure Tailscale Serve", ...)).pipe(as(null))`. By contrast, `t3 pair --tailscale` fails loudly in the same situation (`TailscaleServeFailedError`).

### Impact

Major degradation or frequent failure

### Version or commit

0.0.45 (t3code-bin 0.0.45-1, Omarchy package)

### Environment

Omarchy 4.0.4 (Arch), Linux 7.2.5, tailscale 1.102.3

### Logs or stack traces

```shell
Failed to configure Tailscale Serve
```

### Workaround

Run `sudo tailscale set --operator=$USER` once, make sure MagicDNS and HTTPS certificates are enabled for the tailnet, then restart the server.

### Related

The missing way to enable Serve for `t3 service install` is proposed separately in Ideas: #16243