Skip to content

sbx: VM clock drift is fixed; remove troubleshooting step #25152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvdksn merged 1 commit into from
May 22, 2026
Merged

sbx: VM clock drift is fixed; remove troubleshooting step #25152

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 0 additions & 18 deletions content/manuals/ai/sandboxes/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,24 +185,6 @@ isn't configured, use one of these workarounds:
This replays each commit on the branch and re-signs it with your local
signing key.

## Clock drift after sleep/wake

If your laptop sleeps and wakes while a sandbox is running, the VM clock can
fall behind the host clock. This causes problems such as:

- External API calls failing because of timestamp validation.
- Git commits with incorrect timestamps.
- TLS certificate errors due to time mismatches.

To fix the issue, stop and restart the sandbox:

```console
$ sbx stop <sandbox-name>
$ sbx run <sandbox-name>
```

Restarting the sandbox re-syncs the VM clock with the host.

## Daemon fails to start after downgrading

If you downgrade `sbx` to a version older than the one that last managed your
Expand Down