From f29da0c32e836b751916bb4ed4c44ac1d8a99dba Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Fri, 22 May 2026 11:51:47 +0200 Subject: [PATCH] sbx: VM clock drift is fixed; remove troubleshooting step Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com> --- .../manuals/ai/sandboxes/troubleshooting.md | 18 ------------------ 1 file changed, 18 deletions(-) diff --git a/content/manuals/ai/sandboxes/troubleshooting.md b/content/manuals/ai/sandboxes/troubleshooting.md index 116b7bea6a8..0430031207d 100644 --- a/content/manuals/ai/sandboxes/troubleshooting.md +++ b/content/manuals/ai/sandboxes/troubleshooting.md @@ -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 -$ sbx run -``` - -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