[Bug]: T3 Connect CLI GitHub sign-in returns 500 FUNCTION_INVOCATION_FAILED

Before submitting

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

Area

Not sure

Steps to reproduce

1. On a Fedora Linux machine, run:

   npx t3@latest connect
   

2. The CLI prints a browser URL and waits for an authorization code to be pasted back into the terminal.

3. Open the generated URL in Google Chrome.

4. Choose GitHub as the sign-in method and sign in with a GitHub account.

5. The browser reaches an accounts.t3.codes/sign-in URL whose redirect points to the /auth-consent flow.

6. Instead of showing the consent/code page, the hosted page displays a server error.

The complete authorization URL is intentionally omitted because it may contain temporary authentication parameters.

Observed on September 15, 2026, at approximately 10:52 AM Eastern.

Expected behavior

After GitHub authentication, the browser should show the T3 Connect authorization/consent result and provide the code needed by the waiting t3 connect process. The Fedora environment should then be linked to the T3 account.

Actual behavior

The browser displays:

This page is temporarily unavailable
A function needed by this page failed.

500 FUNCTION_INVOCATION_FAILED
yul1::pfh97-1789483902569-f81f3c242689

The authorization flow cannot complete and the CLI remains unable to link the Fedora environment.

This appears to fail on the hosted accounts.t3.codes page before the authorization code is returned, rather than during the desktop application's post-OAuth callback handling.

Impact

Major degradation or frequent failure

T3 Connect cannot be configured through the documented CLI flow. Other remote-access methods may still be available.

Version or commit

Latest version resolved by npx t3@latest connect on September 15, 2026. The exact resolved version was not captured.

Environment

• CLI host: Fedora Linux
• Command: npx t3@latest connect
• Browser: Google Chrome
• Authentication provider: GitHub
• Hosted authentication domain: accounts.t3.codes

Logs or stack traces

500 FUNCTION_INVOCATION_FAILED
yul1::pfh97-1789483902569-f81f3c242689

No terminal error was produced before the browser failure; the CLI was waiting for the authorization code.

Screenshots, recordings, or supporting files

A screenshot was captured showing the hosted error page and the invocation ID. The authorization URL was redacted.

Workaround

Desktop-managed SSH or direct Tailscale pairing may bypass T3 Connect account authentication, but neither workaround has been verified as part of this reproduction.

Related issue

#7512 concerned an OAuth flow that reached the desktop callback and then displayed a Not Found route. This report appears different because the hosted accounts.t3.codes page itself returns HTTP 500 before the consent/code step completes.

Start by reproducing npx t3@latest connect on Fedora and follow the generated URL through GitHub sign-in to the hosted accounts.t3.codes/sign-in and /auth-consent flow. Inspect the hosted authentication path associated with the reported invocation ID and compare it with related issue #7512. Done means GitHub sign-in returns the consent page and authorization code so the waiting CLI can link the environment.