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
[Bug]: Daytona runs get stuck in provisioning because SSH token expiry exceeds the API limit #4494
Daytona creates and starts the sandbox, but the run stays in provisioning. Each attempt to create SSH access fails with HTTP 400. The task's commands never run.
Expected behaviour
dstack establishes SSH access and the run reaches running.
dstack version
Reproduced from source at c9528229c, configured to use runner 0.22.8. The affected Daytona backend code is identical on master at d616872d6.
Server logs
Got exception when updating instance pr286-e2e-0 provisioning data
DaytonaAPIError: Daytona API returned HTTP 400: expiresInMinutes must be between 1 and 1440
Possible fix: Restore support for long SSH-token expiries in Daytona, or handle credential expiry and renewal in dstack. Reducing the request to 24 hours would unblock startup, but would leave reconnection after expiry unresolved.
Reproduced through the Python client and an isolated dstack server on a real H200 while reviewing dstackai/gpuhunt#286. That PR changes GPU discovery, not SSH setup; this issue affects the existing dstack integration.
Activity