[Bug]: T3 Connect fails to open environment: endpoint_request_failed on Windows → iOS

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

Steps to reproduce

1. Run T3 Code 0.0.36 on a Windows x64 PC.

2. Enable T3 Connect and link the environment using t3 connect link.

3. Confirm t3 connect status reports:

   • Exposure: enabled
   • Authorization: stored credential
   • Environment link: provisioned

4. Open the T3 Connect iOS app (version 1.0.3).

5. Select the Windows environment.

6. Observe that the environment and live session data are visible.

7. Attempt to open the T3 environment/thread.

8. The connection fails and repeatedly shows:
   Failed to connect. Reconnecting...
Reason: Relay environment endpoint is unavailable: endpoint_request_failed

9. Signing out/in and restarting T3/Cloudflared does not resolve the issue.

Expected behavior

Expected behavior

The iOS client should successfully establish a relay connection to the provisioned Windows T3 environment and open the selected thread/session.

The environment is already discoverable and live session data is available, so opening the environment should not fail with endpoint_request_failed.

Actual behavior

Actual behavior

The iOS app successfully discovers the Windows environment and displays live session data, but opening the environment/thread fails.

The app repeatedly shows:

Failed to connect. Reconnecting...
Reason: Relay environment endpoint is unavailable: endpoint_request_failed

The issue persists after signing out and back in, re-linking T3 Connect, and restarting T3/Cloudflared.

The local T3 environment is reachable and responding correctly on 127.0.0.1:3773, and T3 Connect reports exposure as enabled with a stored authorization credential.

Impact

Blocks work completely

Version or commit

T3 CLI/server: 0.0.36 T3 - iOS: 1.0.3 - Cloudflared: 2026.5.2

Environment

Host OS: Windows x64 - Client: T3 Code iOS 1.0.3 T3 - Connect relay: https://relay.t3.codes

Logs or stack traces

Failed to connect. Reconnecting...
Reason: Relay environment endpoint is unavailable: endpoint_request_failed

Trace ID: 3b4c5cf5a3bf5af6788ace70ab71afa8
Environment ID: 18640124-fc80-48c5-a37a-b5b3b7b9f095

Screenshots, recordings, or supporting files

No response

Workaround

No response

Start in apps/server and trace the relay endpoint flow used by t3 connect link and t3 connect status, then compare it with the iOS attempt against relay.t3.codes. Use the provided Trace ID and Environment ID while reproducing with the Windows environment and local endpoint at 127.0.0.1:3773. Done means the iOS client can open the provisioned environment/thread without endpoint_request_failed.