Settings lost after update to v5.0.6 // No action or error after manual backup

Hi,

Sorry to hear about the trouble after updating. Since your FTP credentials and settings were reset, it’s possible that something didn’t fully migrate during the update.

A few things to try:

• Clear Cache: If you’re using any caching plugins, try clearing them and then test the backup again.
• Check Logs: Even if an error isn’t showing, you can check for any related logs under BackWPup > Logs to see if there’s any indication of what’s happening.
• Try Reinstalling: If the issue persists, try uninstalling and reinstalling BackWPup to ensure all settings are properly applied.
• Direct Testing: If backups are still not running, temporarily switch the destination to “Local” and see if it works there. This could help narrow down if it’s an FTP-specific issue.

If none of these resolve the problem, feel free to reach out directly, and we can investigate further.

Dear @saranshwpm,

thanks for your feedback!

• Clear Cache: No caching plugins in place.
• Check Logs: No logs have been created. Also, in the backup history no entry is made.
• Direct Testing: Activated “Local” as well – but still no backup, backup history entry or log is created.

Update to v5.0.7 has been made, but no changes as well.

Try Reinstalling would be the next and final step. Do you recommend to delete the plugin completely and install again and setup again from scratch? Or any other way that is recommended?

Thanks!

Dear @saranshwpm & to whom it may concern,

I reinstalled completely, so removed the plugin completely, installed and set up from scratch. This worked. No the plugin is functional again – just updating directly was breaking its functionality.

Thanks!

• This reply was modified 2 weeks, 3 days ago by David181.

In case someone else finds this issue, for me with the same problem, the cultprit was under Advanced Settings -> Network, my authentication method was removed and I needed to reset it after updating.

For developers, having a silent error like this was very frustrating as there were no messages or logs to debug.

I noticed that as well, but adding the relevant information again didn’t solve it for me. I had to take the steps above and needed to re-install the plugin from scratch.