Troubleshooting Common Issues
Before submitting a support ticket, please check if your issue is covered in these common troubleshooting scenarios.
Common Error Codes
This happens when your backup takes longer than your hosting provider allows PHP scripts to run (often 30-60 seconds on shared hosting).
Solution: Go to IPow Core → Settings → Advanced Tab, and enable "Chunked Processing". You can also lower the chunk size to 2MB or 5MB if the problem persists. Alternatively, ask your web host to increase the max_execution_time in your PHP.ini to 120 or 300 seconds.
Your connected cloud storage (e.g., Google Drive) is out of free space. IPow Core cannot upload the backup archive.
Solution: Delete old files from your cloud storage drive, or purchase a larger storage plan from your provider. IPow Core handles its own retention limits, but it cannot delete files outside of its designated backup folder.
The restore script cannot connect to the MySQL database because the credentials provided are incorrect or the database server is down.
Solution: Verify that your wp-config.php file has the correct DB_USER, DB_PASSWORD, and DB_HOST. If you are migrating to a new server, you must update these values to match the new server's database credentials.
Your site structure is massive, and attempting to zip the entire wp-content/uploads directory in one pass is hitting your PHP memory_limit.
Solution: Enable "Chunked Processing" in Advanced settings. You can also exclude large, non-essential folders (like cache folders) by going to IPow Core → Settings → Exclusions.
How to Generate a Debug Log
If you are experiencing an issue not listed here and need to contact support, please attach a debug log. This helps our engineers identify the exact line of code causing the failure.
1. Go to IPow Core → Settings → Advanced
2. Toggle "Enable Debug Logging" to ON
3. Click Save Changes
4. Run a manual backup to trigger the error again
5. Click "Download Debug Log" and attach it to your support ticket