Repository navigation
T3 Connect fails to publish environment with "invalid_signature_or_scope" on v0.0.45 #19034
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
Install T3 Code v0.0.45 on Windows 11.
Sign in successfully.
Verify that the mobile device is signed in with the same account.
Open Settings → Connections.
Enable T3 Connect.
Click Continue to publish the environment.
T3 Code sends a request to relay.t3.codes.
The request fails with "Relay rejected the environment link proof (invalid_signature_or_scope)".
No environment appears under Account → T3 Connect.
Expected behavior
The environment should be published successfully through T3 Connect, appear under Account → T3 Connect, and become available from the mobile application.
Actual behavior
Publishing the environment fails with:
Relay rejected the environment link proof (invalid_signature_or_scope)
The environment is never created and Account → T3 Connect remains empty.
Impact
Major degradation or frequent failure
Version or commit
T3 Code v0.0.45 (Stable)
Environment
Windows 11 T3 Code v0.0.45 (Stable) GitHub account connected Mobile app installed and signed in with the same account Network Access enabled
Logs or stack traces
POST https://relay.t3.codes/v1/client/environment-links
Failed to load resource: the server responded with a status of 400
[t3-connect] Could not update T3 Connect
Relay rejected the environment link proof
(invalid_signature_or_scope)
Trace ID:
5943c4fcde879efd03faf3d4a6d9bb9cScreenshots, recordings, or supporting files
Workaround
No workaround found.
I tested:
Signing out and signing back in.
Reinstalling T3 Code.
Logging in using GitHub.
Verifying the same account is used on desktop and mobile.
Creating a new pairing link.
Using Network Access instead of T3 Connect.
None of these steps resolved the issue.
Activity
juliusmarminge commentedon Oct 13, 2026
Note
Grok responding on behalf of Julius.
We can't act on this from the client yet.
invalid_signature_or_scopeis one relay reason shared by four different checks ininfra/relay/src/environments/EnvironmentLinker.ts:scopesdon't cover what was requested (managed_tunnels, oragent_activity_notificationswhen notifications or Live Activities are on)An expired proof has its own error (
environment_link_proof_expired), so this isn't plain expiry. Re-signing in or reinstalling won't change it, because the proof is signed by the environment's own key, not your account. We'll look up your trace ID on the relay side to see which check failed.Meanwhile, please:
If none of these help, reply with the results and we'll take it from there.
FabioBRodrigues commentedon Oct 13, 2026
Resolved.
The root cause was the local Windows clock being out of sync.
After correcting the system time and re-enabling T3 Connect, the environment was published successfully.
The error message was:
Relay rejected the environment link proof (invalid_signature_or_scope)
which appears to have been caused by the invalid local time affecting the proof validation process.
Thanks for the help.
callmearta commentedon Oct 18, 2026
The issue for me as well was the clock being out of sync by just a couple of minutes, fixing the clock fixed the problem.
Thanks @FabioBRodrigues
t3dotgg commentedon Oct 21, 2026
Note
🤖 Claude Opus 5.5 responding on behalf of Theo
Thanks for the report. This is fixed on main in #19640. Please test on the nightly built from main on 2026-10-21, or on the next stable release. If the problem still occurs there, please open a new issue that links to this one, with your version and steps to reproduce it.