bcrodua

Hi Ray,

Thank you for your message.

You are correct that UpdraftPlus first creates the backup locally in the wp-content/updraft folder before uploading it to remote storage and then deleting it (if local deletion is enabled). Because of that, the plugin still requires write access to the UpdraftPlus folder.

If your host has completely blocked write access to that directory, then unfortunately UpdraftPlus will not be able to function correctly, even with remote storage enabled.

I’ll report this feedback to our team as well, as more hosts seem to be applying these kinds of restrictions.

Kind regards,
Bryle

Hi,

Yes, you can exclude those files.

MacOS ._ files are metadata files created by Finder and are not needed for WordPress backups or restores. You can exclude them using the UpdraftPlus exclude rules under: Settings → Exclude files from backup

You can add patterns such as: ._* and optionally: .DS_Store

These files should not normally be required and excluding them can help avoid issues during restore/import.

Kind regards,
Bryle

Hi,

This can happen if a backup process did not complete successfully or if scheduled backups are overlapping. In such cases, old backup sets may not be cleaned up immediately according to the retention settings.

Please share your backup log so we can check whether there are any failed or incomplete backups preventing cleanup.

Thanks,
Bryle

Hi,

If you’re moving the site to a different URL/domain, this requires the Premium version with the Migrator add-on, which handles the URL changes automatically during the restore process.

Best Wishes,
Bryle

Hi,

UpdraftPlus should not uninstall itself, so something external is likely removing or deleting the plugin files.

A few common causes are security plugins, hosting security scanners, malware cleanup tools, automatic management tools, or server processes removing files.

Could you check whether the plugin is actually being deactivated or if the UpdraftPlus plugin folder disappears completely from wp-content/plugins/? Also, if possible, check whether there are any hosting/security logs around the time this happens.

That may help narrow down what is removing it.

Best Wishes,
Bryle

Hi,

The error suggests that UpdraftPlus can connect to the OVH container successfully, but the upload request signature does not match what OVH expects.

Please double-check that the Access Key, and Secret Key are all entered correctly. It may also help to generate a fresh set of OVH credentials and test again.

Since the container itself is reachable, this is most likely related to the authentication/signing configuration rather than a connection issue.

Best Wishes,
Bryle

Hi,

Thanks for sharing the full log.

I can see the warning at 0140.170, but the backup itself completed successfully at the end of the log. This appears to be a PHP warning rather than a backup failure.

I’ve passed this on for review, but for now there’s no action needed on your side as long as the backups are completing successfully.

Thanks again for reporting it.

Best Wishes,
Bryle

Hi,

This indicates that the backup is failing because the server is running out of available memory while closing/creating the ZIP archive.

Please try reducing the Split archives every setting in UpdraftPlus, for example to 100MB or lower, then run the backup again.

If it still fails, please ask your host to check the PHP memory limit and server resource limits, as the error is coming from the server environment not being able to allocate enough memory during the backup process.

Best Wishes,
Bryle