[Bug]: Misleading server link for --host 0.0.0.0 address

Open Beginner friendly

#8,384 opened on Aug 27, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 70/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: node.js, typescript
Domain: backend

Research direction

Start in apps/server and reproduce the issue with t3 serve --port 5173 --host 0.0.0.0 in the described Docker environment. Trace how the Connection string and Pairing URL are generated; done means the pairing link uses the explicitly supplied host instead of the container IP.

Written by the indexing model from the issue text.

Description

bug needs-triage

Before submitting

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

Area

apps/server

Steps to reproduce

On the macOS 15 host in Ubuntu 24 Docker container i run

t3 serve --port 5173 --host 0.0.0.0 --port 5173
# ... =>
17:26:10.808] INFO (#239): Listening on http://0.0.0.0:5173
[17:26:10.825] INFO (#238): agent activity publishing standby; waiting for T3 Connect link reconciliation
[17:26:10.826] INFO (#238): provider.session.reaper.started
  { inactivityThresholdMs: 1800000, sweepIntervalMs: 300000 }
T3 Code server is ready.
Connection string: http://172.18.0.2:5173
Token: XTRR7LH9WNTQ
Pairing URL: http://172.18.0.2:5173/pair#token=MYTOKEN

Listening on http://0.0.0.0:5173 - is correct, and it works, but http://172.18.0.2:5173/pair#token=MYTOKEN is not. The server fetches the container IP instead of the host that user provided explicitly

Expected behavior

# ...
Pairing URL: http://0.0.0.0:5173/pair#token=MYTOKEN

Actual behavior

# ...
Pairing URL: http://172.18.0.2:5173/pair#token=MYTOKEN

Impact

Cosmetic issue

Version or commit

0.0.35

Environment

macOS 15.5, node 26.7

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround