-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Start by collecting version, install path, logs, and health output.
convex-autobackup --version
convex-autobackup doctor --json
curl http://localhost:8976/api/v1/healthCheck logs:
docker logs convex-autobackupCheck container state:
docker ps -a
docker inspect convex-autobackupCommon causes:
- Missing or invalid
CONVEX_AUTOBACKUP_MASTER_KEY. -
/datavolume is not writable. - Port
8976is already in use. - Host cannot download the managed Convex runner.
Confirm the app is listening:
curl http://localhost:8976/api/v1/healthConfirm Docker port mapping:
docker psIf remote:
- Check firewall rules.
- Check reverse proxy config.
- Confirm DNS points at the right host.
- Confirm HTTPS certs are valid.
Bootstrap is only available before the first user exists. After owner creation, use normal login or owner/admin user management.
If you lost owner access, stop and inspect your data backup plan before changing the database manually.
Check:
- Deploy key is valid.
- Deployment name exactly matches the intended Convex deployment.
- Deploy key can access the project.
- Host can reach Convex services.
- Managed runner is installed:
convex-autobackup runner install --json
convex-autobackup doctor --jsonPossible causes:
- Destination write was interrupted.
- Object storage returned stale or partial data.
- Local disk corruption or manual file changes.
- Manifest/archive pair no longer match.
Do not delete the failed artifact until you understand whether it is the only copy for that time window.
Restore requires exact deployment confirmation:
convex-autobackup restore \
--run-id <run-id> \
--target-id <target-id> \
--confirm-deployment <deployment-name> \
--jsonUse the deployment name shown in the target. This guard is intentional.
Update Rust:
rustup update stable
cargo install convex-autobackup --version 0.1.0-beta.1If the release was just published, crates.io indexing may take a few minutes.
Check the release workflow:
https://github.com/KodyDennon/ConvexAutoBackup/actions/workflows/release.yml
Then check the release:
https://github.com/KodyDennon/ConvexAutoBackup/releases/latest
If one channel published but another failed, the workflow is designed so reruns can skip already-published crates at the same version.
- README: https://github.com/KodyDennon/ConvexAutoBackup#readme
- Deployment docs: https://github.com/KodyDennon/ConvexAutoBackup/blob/main/docs/DEPLOYMENT.md
- Open source release docs: https://github.com/KodyDennon/ConvexAutoBackup/blob/main/docs/OPEN_SOURCE_RELEASE.md
ConvexAutoBackup docs: Repository · Releases · Docker Hub · crates.io