Troubleshooting

Fixes for common Nimbus errors.

Error: target unreachable

Nimbus can’t reach the configured target. Check:

1. The URI scheme matches an installed provider (s3://, gs://).
2. Network access to the endpoint isn’t blocked by a firewall or VPN.
3. nimbus config validate doesn’t report a malformed target.

Error: access denied

Credentials are missing or lack permission. Confirm NIMBUS_ACCESS_KEY / NIMBUS_SECRET_KEY are set (see Authentication) and that the underlying IAM policy grants PutObject/GetObject on the target bucket.

Sync hangs with no output

Usually means watch is waiting on the batchDelay window (see Sync Strategies). Run with --verbose to confirm:

nimbus watch --verbose

Files re-upload every sync

Caused by a tool rewriting mtimes on every save (some editors and CI checkouts do this). Switch the change-detection mode to content hashing:

nimbus config set diffMode hash

This is slower on large workspaces but immune to mtime churn.