You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Allow configurable timeout and retry for SSH environments
#29552
I was running T3 Code with a remote environment. Because of the job the agent was running, the remote was "slightly" under pressure (load in the 50s, sub-100 MB RAM left). SSH was still possible if you could wait a minute to log in. However, T3 Code timed out within seconds. It seems there is no setting right now to adjust the timeout, nor the retry time.
T3 Code connection to xxx: T3 Code on xxx did not answer
This device: ok
T3 Code on xxx: FAILED
Cause: remote-unavailable
Attempts: 8
Next retry: 2026-11-02T20:00:05.542Z
Route: Direct
App version: 0.1.6
Host version: 0.1.6
Error: Could not prepare the SSH environment: Error invoking remote method 'desktop:ensure-ssh-environment': SshCommandError: Connection timed out during banner exchange
Connection to 192.168.0.2 port 22 timed out
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I was running T3 Code with a remote environment. Because of the job the agent was running, the remote was "slightly" under pressure (load in the 50s, sub-100 MB RAM left). SSH was still possible if you could wait a minute to log in. However, T3 Code timed out within seconds. It seems there is no setting right now to adjust the timeout, nor the retry time.
All reactions