T3 Code real server | AFTER | e31099fb04d4c6905e66535720bb64e37ab12726
Environment: Linux x64, built server, fresh empty database, unlinked.
Transport: HTTP port 18326; non-loopback interface on the same VM.
Capture: chronological runtime transcript; credentials and interface IP omitted.
POST /oauth/token [startup pairing credential; never printed]
HTTP 200; authenticated paired-client bearer session issued.

Direct non-loopback authority -> POST /api/connect/link-proof
Payload: tunnel endpoint environment.example.test; origin 127.0.0.1:18326.
HTTP 400
{"_tag": "EnvironmentHttpBadRequestError", "message": "T3 Connect can only be turned on from the
machine running this environment. On that machine, use Settings → Sharing & access or run `t3
connect link`."}

Forwarded host authority -> POST /api/connect/link-proof
Payload: tunnel endpoint environment.example.test; origin 127.0.0.1:18326.
Headers: {"x-forwarded-host": "environment.example.test"}
HTTP 400
{"_tag": "EnvironmentHttpBadRequestError", "message": "T3 Connect can only be turned on from the
machine running this environment. On that machine, use Settings → Sharing & access or run `t3
connect link`."}

Forwarded protocol authority -> POST /api/connect/link-proof
Payload: tunnel endpoint environment.example.test; origin 127.0.0.1:18326.
Headers: {"x-forwarded-proto": "https"}
HTTP 400
{"_tag": "EnvironmentHttpBadRequestError", "message": "T3 Connect can only be turned on from the
machine running this environment. On that machine, use Settings → Sharing & access or run `t3
connect link`."}

Completed. No relay contacted; all three requests refused.