Common Errors and Fixes
| Symptom | Likely Cause | Action |
|---|---|---|
403 Forbidden on test connection |
Wrong key type, policy, region, or namespace mismatch | Use OCI customer secret key pair, verify region + namespace + bucket and IAM policy. |
PutObject requires non-empty Bucket |
OCI selected without valid bucket settings | Configure OCI bucket or switch destination to Local. |
Encryption key required |
Encryption enabled without key | Set encryption key in Settings, then save again. |
| Backups not listed | Folder/prefix changed or list not refreshed | Refresh backup list and verify Backup Folder Name/prefix in Settings. |
If Backup Looks Stuck
- Check progress text in backup tab.
- Open
Logsand inspect latest operation. - Verify available disk space in uploads temp folder.
- Try Local destination only to isolate OCI transfer latency.
- If encryption is enabled on huge files, expect additional processing time.
If Schedules Do Not Start On Time
- Open Schedules and confirm the schedule is enabled.
- Click Run now to validate schedule payload.
- Check next run time is moving forward after execution.
- Generate normal wp-admin traffic to trigger WP-Cron if needed.
- Review logs for scheduler failures.
Backora runs due-check logic from scheduled hook and admin fallback, but WP-Cron still requires
site traffic.
If Email Notifications Are Not Sent
- Enable Email Notifications in Backora Settings.
- Set Notification Email.
- Install and configure an SMTP plugin.
- Test WordPress email separately before relying on backup notifications.
Collect a Support Bundle
- Latest operation log from Logs tab.
- Screenshot of Settings tab (mask keys/secrets).
- Destination type and backup mode used.
- Exact error message + timestamp.
- WordPress timezone setting and current server time.
Still Need Help?
If the troubleshooting steps above didn’t resolve your issue, the Backora Support Center is here to help.