• Resolved pleinx

    (@pleinx)


    Hello UpdraftPlus Support Team,

    I’m experiencing an issue with scheduled backups in UpdraftPlus.

    The plugin was freshly installed, Google Drive was set up successfully, and manual backups work and sync correctly.

    However, the automatic cron schedules do not behave as expected. Configuration

    UpdraftPlus → Settings

    • Files backup: Every 2 hours
    • Database backup: Every hour

    (I also tried other intervals — same behavior.) Cron overview (UpdraftPlus → Advanced → Cron events)

    updraftplus_clean_temporary_files Twice daily Next run: 8 February 2026 22:15 (in ~11h 50m) updraft_backup Every 2 hours Next run: 8 February 2026 23:20 (in ~12h 56m) updraft_backup_database Every hour Next run: 8 February 2026 23:20 (in ~12h 56m)

    So even with hourly / 2-hour schedules, the next execution is always pushed 12–13 hours into the future. Database check

    In the WordPress options table (wp_options), the cron entries look correct:

    updraft_backup_database → everyhour (3600) updraft_backup → every2hours (7200)

    The intervals are correct, but the timestamps are always far in the future. What I already tried

    • Manual backups (successful, but do not affect next scheduled run)
    • Changing schedules (manual → hourly / 2h → save)
    • Triggering wp-cron externally via system cron
    • Deleting and re-saving UpdraftPlus settings
    • Verified timezone (correct)
    • Verified wp-cron execution (triggered hourly by cronjob)
    • Enough site traffic
    • No caching plugin active
    • define('DISABLE_WP_CRON', true); is not set

    Attempted workaround (manual cron reset)

    I also tried explicitly deleting and re-scheduling the cron events via code:

    add_action('init', function () {
    if (!current_user_can('manage_options')) return;
    if (!isset($_GET['updraft_cron_reset'])) return;

    wp_clear_scheduled_hook('updraft_backup');
    wp_clear_scheduled_hook('updraft_backup_database');
    wp_clear_scheduled_hook('updraftplus_clean_temporary_files');

    $now = time() + 60;
    wp_schedule_event($now, 'every2hours', 'updraft_backup');
    wp_schedule_event($now, 'everyhour', 'updraft_backup_database');
    wp_schedule_event($now, 'twicedaily', 'updraftplus_clean_temporary_files');

    wp_die('Updraft cron events reset');
    });

    Does also not work. Cron events are “0 minutes 0 secs” and after change in plugin settings returns to ~12h.

    Expected behavior
    If backups are set to:

    • Database: every hour
    • Files: every 2 hours
    • This topic was modified 3 months ago by pleinx.
    • This topic was modified 3 months ago by pleinx. Reason: added image from settings
    • This topic was modified 3 months ago by pleinx.
Viewing 15 replies - 1 through 15 (of 22 total)
  • Thread Starter pleinx

    (@pleinx)

    Update (not solved):

    • Automated backup does not work. Also with this wrong timers.
    • When i now click under cron events i can only see “updraftplus_clean_temporary_files”. The other two are gone.
    Plugin Support vupdraft

    (@vupdraft)

    Can you install the free plugin WP Crontrol and go to your Cron Events?

    Are any of the events showing as overdue?

    Thread Starter pleinx

    (@pleinx)

    Thanks for your reply 🙂

    I’ve already installed this plugin, because it was mentioned in your troubleshooting guide

    • First of all: There was no cronjob in the WP Control plugin mentioned for updraft besides the cleanup for temp files
    • I checked the same under your plugin > cron events > no cronjobs besides cleanup task found
    • i saved again the settings
    • now i can see the cronjobs in your and WP Control plugin
    • After the timer is running down the 12 hours, the cronjobs seems to be lost and also no backup triggered (i checked google drive > updrafts folder > no new backups since days)
    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Can you post your php error log using a tools such as pastebin.com?

    Thread Starter pleinx

    (@pleinx)

    Yes, sure, i have debugging enabled since i noticed this issue. Here are some logs:

    https://pastebin.com/eTrRNqwN

    Plugin Support vupdraft

    (@vupdraft)

    Have you filtered out the UpdraftPlus ones?

    It would be really helpful to see all of them

    Thread Starter pleinx

    (@pleinx)

    Yes, i filtered them out. Is it possible to contact you more privacy with the logging-data?

    Thread Starter pleinx

    (@pleinx)

    Okay, it looks like I found the issue myself!

    The wp-content folder had permissions set to 705 instead of 755/750. After correcting this, I can now see the cron events with the correct timers.

    I’ll provide final feedback after 1–2 days of testing 🙂
    Maybe this is something you could pass on to your developers — for example, UpdraftPlus could check the permissions of relevant folders automatically?

    • This reply was modified 3 months ago by pleinx.
    Thread Starter pleinx

    (@pleinx)

    Okay, sadly this also did not fix the issue.

    For a short moment I could see correct timers, but today it is again always +13 hours, and the backups are not executed at all (not even after those 13 hours have passed).

    What I tested today:

    • Reset UpdraftPlus plugin (again)
    • Deleted all UpdraftPlus-related entries from the database
    • Verified directory permissions (0755) and file permissions (0644)
    • Restored the site on another hoster (where it works fine for my other client installations)
    • Installed a completely fresh WordPress on a known working hoster and installed only UpdraftPlus

    In all cases, the issue persists on this specific environment.

    At this point I am fairly certain the issue is related to either:

    • datetime handling (timezone / UTC offset / server time mismatch),
    • cron execution,
    • file system permissions,
    • or possibly a regression in the latest UpdraftPlus update.

    It is worth mentioning that this behavior does not occur on my other installations (same plugin version), which suggests an environment-specific trigger.

    One important observation:

    If I manually set the “next cron date” via WP Crontrol so that it matches the intended interval (Files → every 2 hours, Database → every 1 hour), everything works perfectly.
    As long as I do not save the UpdraftPlus settings again, the cron jobs execute correctly and the backups are successfully uploaded to Google Drive.

    The issue only reappears immediately after saving the UpdraftPlus settings, when the next run is rescheduled to +13 hours again.

    • This reply was modified 2 months, 4 weeks ago by pleinx.
    Plugin Support vupdraft

    (@vupdraft)

    Hi,

    Can you post your php error log using a tools such as pastebin.com

    Thread Starter pleinx

    (@pleinx)

    Pastebin does not allow some content of my logfile so store. However, i sorted it out

    - PHP Deprecated: UDP_Google_Http_REST::decodeHttpResponse(): Implicitly marking parameter $client as nullable is deprecated, the explicit nullable type must be used instead
    File: /wp-content/plugins/updraftplus/includes/Google/Http/REST.php (Line 73)

    - PHP Deprecated: html_entity_decode(): Passing null to parameter #1 ($string) of type string is deprecated
    File: /wp-includes/widgets.php (Line 1652)

    - WordPress database error: Unknown column 'content' in 'WHERE'
    Table: wp_gusbi_post_views (triggered in Admin Posts / Post Views Counter Traffic Signals)

    - PHP Warning: Undefined array key 0
    File: /wp-content/plugins/updraftplus/includes/class-wpadmin-commands.php (Line 941)

    - PHP Warning: Trying to access array offset on null
    File: /wp-content/plugins/updraftplus/includes/class-wpadmin-commands.php (Line 963)

    - PHP Notice: Function _load_textdomain_just_in_time was called incorrectly (wordfence domain loaded too early)
    File: /wp-includes/functions.php (Line 6131)

    - PHP Notice: Function _load_textdomain_just_in_time was called incorrectly (post-views-counter domain loaded too early)
    File: /wp-includes/functions.php (Line 6131)

    - PHP Warning: mysqli_real_connect(): (HY000/1226): User has exceeded the 'max_user_connections' resource (current value: 20)
    File: /wp-includes/class-wpdb.php (Line 1994)

    - Cron Reschedule Error: Hook cmplz_every_five_minutes_hook
    Error: could_not_set (Cron event list could not be saved)

    - Cron Reschedule Error: Hook wp_privacy_delete_old_export_files
    Error: could_not_set (Cron event list could not be saved)

    - Cron Unschedule Error: Hook wordfence_batchReportFailedAttempts
    Error: could_not_set (Cron event list could not be saved)

    - Cron Unschedule Error: Hook wordfence_completeCoreUpdateNotification
    Error: could_not_set (Cron event list could not be saved)

    - PHP Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated
    File: /wp-content/themes/Avada/includes/class-awb-custom-auth-pages.php (Line 87)

    - Info: Automatic updates starting...
    - Info: Automatic updates complete.

    These are looking related maybe?

    [20-Feb-2026 12:22:06 UTC] Cron-Unschedule-Event-Fehler für Hook: wordfence_batchReportFailedAttempts, Fehlercode: could_not_set, Fehlermeldung: Die Cron-Ereignisliste konnte nicht gespeichert werden., Daten: {"schedule":false,"args":[]}

    [20-Feb-2026 19:08:14 UTC] PHP Deprecated: UDP_Google_Http_REST::decodeHttpResponse(): Implicitly marking parameter $client as nullable is deprecated, the explicit nullable type must be used instead in /homepages/12/d1234567/htdocs/webseiten/foobar.de/wp-content/plugins/updraftplus/includes/Google/Http/REST.php on line 73
    Plugin Support vupdraft

    (@vupdraft)

    Thank you for this

    I see issues relating specifically to saving WordPress scheduled tasks. This is affecting more than just UpdraftPlus (you have the error for multiple plugins)

    You have lots of these:

    Cron Unschedule Error: Hook wordfence_completeCoreUpdateNotification  Error: could_not_set (Cron event list could not be saved)

    Setting up a cron job on your server is the most reliable way to run scheduled events. I would also contact your hosts and ask them to take a look as it looks like there may be a server side issue.

    Thread Starter pleinx

    (@pleinx)

    Thanks also for your time.

    I’ve already implemented the HTTP-Cron since 2 weeks like this:

    https://mydomain.tld/wp-cron.php?doing_wp_cron

    Do you have any hints for me, where i should take a look more deep about file-permissions? I just did what the docs say: 0644 to all files (except wp-config) and 0755 to all folders.

    I’ll check with the hoster about the max-db-connections issue and coming back.

    Plugin Support vupdraft

    (@vupdraft)

    Two weeks would not be enough, we normally say every 1- 5 minutes. I Would also do the following

    – Check if your server or hosting provider has limitations or restrictions on cron jobs. If there are restrictions, you may need to adjust your site’s cron schedules or discuss these restrictions with your hosting provider.

    – If WordPress doesn’t have sufficient permissions to write to the files and folders it needs to, this type of error could occur as a result. Ensure that WordPress is able to write to the wp-cron.php file and the /wp-content/ directory.

    – Try deactivating all of your WordPress plugins temporarily, then reactivating them one by one. This can help to identify whether perhaps one of your plugins is causing this issue.

    – If your PHP memory limit is too low, WordPress may not be able to execute cron jobs effectively. You can try increasing the PHP memory limit in your server configuration (https://woocommerce.com/document/increasing-the-wordpress-memory-limit/)

    Here is a really good on file permissions: https://www.malcare.com/blog/wordpress-file-permissions/

    Thread Starter pleinx

    (@pleinx)

    Two weeks would not be enough, we normally say every 1- 5 minutes. I Would also do the following

    I mean with that i already added a cronjob which runs every 1 minute, but since 2 (or now 3) weeks ago 🙂

    Check if your server or hosting provider has limitations or restrictions on cron jobs. If there are restrictions, you may need to adjust your site’s cron schedules or discuss these restrictions with your hosting provider.

    Will do.

    – If WordPress doesn’t have sufficient permissions to write to the files and folders it needs to, this type of error could occur as a result. Ensure that WordPress is able to write to the wp-cron.php file and the /wp-content/ directory.

    wp-cron.php has 755 (for testing) and /wp-content/ has also 755. I did the same like in your mentioned guide: https://www.malcare.com/blog/wordpress-file-permissions/

    Try deactivating all of your WordPress plugins temporarily, then reactivating them one by one. This can help to identify whether perhaps one of your plugins is causing this issue.

    Yes, i already deleted around 5 plugins incl. Wordfence, but does not help.

    If your PHP memory limit is too low, WordPress may not be able to execute cron jobs effectively. You can try increasing the PHP memory limit in your server configuration

    I also did that and the hoster changed to 786M also 3 weeks ago. No changes.

    What i did today is: I installed latest wordpress (6.9.1) and just installed your plugin. It also fails there on hetzner-webhosting (i’ve multiple sites there, without an issue). Is there maybe the possiblity that your plugin or wordpress itself has right now issues?

Viewing 15 replies - 1 through 15 (of 22 total)

You must be logged in to reply to this topic.