WP_Cron HTTP 429 Error

Thanks in advance to anyone who takes the time to read this and assist ??

Around December 10th 2020 automatic plugin updates stopped occurring on both the staging and live site for one of our customers hosted on GoDaddy Managed WordPress. This led me to investigate WP_Cron by installing the WP-Control plugin. Through WP_Control I found that WP_Cron was reporting the below error:

There was a problem spawning a call to the WP-Cron system on your site. This means WP-Cron events on your site may not work. The problem was:
Unexpected HTTP response code: 429

I have been on to GoDaddy support twice, once with a hang-up after 45 minutes and second with a “it’s a content issue” please try contacting WordPress.

I have tried all the usual troubleshooting; disabled all plugins and reverted to stock theme in staging but no change. I’ve also enabled debug logging but nothing is appearing in the log regards WP_Cron.

Having done yet more googling, it looks possible that the WP-Control plugin I’m using to monitor WP CRON may not work properly on GoDaddy Managed WordPress – something to do with “Non-standard WP_Cron processes – GoDaddy Managed WordPress runs a central cron service with a different server configuration than the front-facing server”.

After a day or two of scratching my head I further investigated using the CLI. Manually calling WP-Cron to execute the jobs due to run “now” seems to have worked; however note the 429 error when querying WP-Cron spawn status and the MySQL errors:

[siteREDACTED@n3nlwpsftp002 html]$ wp cron event list
+————————————+———————+——————-+—————+
| hook | next_run_gmt | next_run_relative | recurrence |
+————————————+———————+——————-+—————+
| action_scheduler_run_queue | 1970-01-01 00:00:01 | now | Non-repeating |
| wp_update_plugins | 1970-01-01 00:00:01 | now | Non-repeating |
| recovery_mode_clean_expired_keys | 1970-01-01 00:00:01 | now | Non-repeating |
| action_scheduler_run_queue | 2020-12-10 12:12:35 | now | 1 minute |
| wp_privacy_delete_old_export_files | 2020-12-10 12:58:35 | now | 1 hour |
| wp_version_check | 2020-12-10 16:58:35 | now | 12 hours |
| wp_update_plugins | 2020-12-10 16:58:35 | now | 12 hours |
| wp_update_themes | 2020-12-10 16:58:35 | now | 12 hours |
| mwp_update_public_keys | 2020-12-11 04:58:19 | now | 1 day |
| recovery_mode_clean_expired_keys | 2020-12-11 04:58:33 | now | 1 day |
| wpseo_home_url_check | 2020-12-11 04:58:36 | now | 1 day |
| flamingo_daily_cron_job | 2020-12-11 04:58:36 | now | 1 day |
| wp_scheduled_auto_draft_delete | 2020-12-11 09:34:33 | now | 1 day |
| wpseo-reindex | 2020-12-11 09:51:33 | now | 1 day |
| wp_scheduled_delete | 2020-12-11 10:05:30 | now | 1 day |
| delete_expired_transients | 2020-12-11 10:05:30 | now | 1 day |
| wp_site_health_scheduled_check | 2020-12-13 04:58:35 | now | 1 week |
| wpseo_ping_search_engines | 2020-12-28 07:08:22 | now | Non-repeating |
| wpseo_permalink_structure_check | 2021-01-06 18:07:41 | now | 1 day |
| wpseo_ryte_fetch | 2021-01-06 18:07:41 | now | 1 week |
| sucuriscan_scheduled_scan | 2021-01-06 18:07:52 | now | 1 day |
+————————————+———————+——————-+—————+
[siteREDACTED@n3nlwpsftp002 html]$ wp cron test
Warning: WP-Cron spawn succeeded but returned HTTP status code: 429 Too Many Requests

[siteREDACTED@n3nlwpsftp002 html]$ wp cron event run –due-now
Executed the cron event ‘action_scheduler_run_queue’ in 0.029s.
Executed the cron event ‘wp_update_plugins’ in 0.962s.
Executed the cron event ‘recovery_mode_clean_expired_keys’ in 0.002s.
Executed the cron event ‘action_scheduler_run_queue’ in 0.011s.
Executed the cron event ‘wp_privacy_delete_old_export_files’ in 0.023s.
Executed the cron event ‘wp_version_check’ in 2.357s.
Executed the cron event ‘wp_update_plugins’ in 0.01s.
Executed the cron event ‘wp_update_themes’ in 0.007s.
Executed the cron event ‘mwp_update_public_keys’ in 0.158s.
Executed the cron event ‘recovery_mode_clean_expired_keys’ in 0.003s.
Executed the cron event ‘wpseo_home_url_check’ in 0.003s.
Executed the cron event ‘flamingo_daily_cron_job’ in 8.898s.
Executed the cron event ‘wp_scheduled_auto_draft_delete’ in 0.112s.
Executed the cron event ‘wpseo-reindex’ in 0.004s.
Executed the cron event ‘wp_scheduled_delete’ in 7.748s.
Executed the cron event ‘delete_expired_transients’ in 0.009s.
Executed the cron event ‘wp_site_health_scheduled_check’ in 3.063s.
Executed the cron event ‘wpseo_ping_search_engines’ in 0.002s.
Executed the cron event ‘wpseo_permalink_structure_check’ in 0.006s.
Executed the cron event ‘wpseo_ryte_fetch’ in 5.017s.
Executed the cron event ‘sucuriscan_scheduled_scan’ in 130.932s.
Success: Executed a total of 21 cron events.

Warning: mysqli_query(): MySQL server has gone away in /home/z47dREDACTED392/html/wp-includes/wp-db.php on line 205 6
Warning: mysqli_query(): Error reading result set’s header in /home/z47dREDACTED392/html/wp-includes/wp-db.php on l ine 2056

After doing this I had hoped all would be well as WP_Control plugin was now showing all the jobs had run, however the next day I took a look and all the jobs that should have run again had not and were reporting “missed schedule”.

Hoping someone can help me here as this is driving me a little nuts ??

• This topic was modified 3 years, 10 months ago by finiterex.