• GoDaddy Community
  • Managed WordPress Hosting
  • Managed WordPress Hosting

    cancel
    Showing results for 
    Show  only  | Search instead for 
    Did you mean: 
    finiterex
    Getting Started

    WP CRON HTTP 429 Error

    Around December 10th 2020 WP CRON stopped working on both the staging and live site for one of our customers.  The error is:

     

    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 support twice, once with a hang-up after 45 minutes and second with a "it's a content issue" and no further assistance.  

     

    I have tried all the usual troubleshooting; disabled all plugins and reverted to stock theme in staging but no change.  I've also tried to enable debug logging but no debug.log is being created in WP-Content on either staging or live.

     

    This issue means no auto updates are occurring. 

     

    Hoping someone can provide some help.

    11 REPLIES 11
    finiterex
    Getting Started

    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 Word Press - 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".

     

    Whether the above is right/wrong, related/unrelated it made me realise I should explain why I started looking into WP CRON issues; early Jan I realised I had not had any "plugins updated..." emails.  I logged into wp-admin and found plugins reporting "failed to auto update".  After manually updating, google led me to WP CRON.

     

    TLDR - The original problem is that plugins are failing to update on both staging and live.  This led me to looking at WP-CRON via the WP Control plugin which led to the "HTTP 429 error".  A bit more googling led to "GoDaddy Managed Wordpress WP Cron is non standard".

     

    Long story short then; help GoDaddy support... preferably 3rd / 4th line please!

    I am amazed no one from GoDaddy has responded... anyway further investigation 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.  Very keen for some comment from GoDaddy as to what is happening here.

     

    [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

    So checked this morning, bunch of WP-Cron jobs have "missed schedule" again.  

     

    Anyone?

    So still not working and am at a loss as to what's going on... I can trigger run from the CLI but not the GUI, and auto run clearly isnt happening.  GoDaddy support need your help!

     

    finiterex_0-1610356302121.png

     

    So I manually ran each job from the CLI with no issue... but still the jobs are not auto triggering. Even when I tried going to http://www.yourwebsite.com/wp-cron.php?doing_wp_cron/?nocache=1 (or the HTTPS version) the WP_Cron jobs didn't trigger.

    Below is the output of manually running each job from the CLI. I'm now back on the phone with GoDaddy... wish me luck!

    [REDACTED@n3nlwpsftp002 html]$ wp cron event list
    +------------------------------------+---------------------+-------------------+------------+
    | hook | next_run_gmt | next_run_relative | recurrence |
    +------------------------------------+---------------------+-------------------+------------+
    | action_scheduler_run_queue | 2021-01-08 13:35:35 | now | 1 minute |
    | wp_privacy_delete_old_export_files | 2021-01-08 13:58:35 | now | 1 hour |
    | wp_version_check | 2021-01-08 16:58:35 | now | 12 hours |
    | wp_update_plugins | 2021-01-08 16:58:35 | now | 12 hours |
    | wpseo_permalink_structure_check | 2021-01-08 18:07:41 | now | 1 day |
    | sucuriscan_scheduled_scan | 2021-01-08 18:07:52 | now | 1 day |
    | wp_update_themes | 2021-01-09 01:25:42 | now | 12 hours |
    | mwp_update_public_keys | 2021-01-09 04:58:19 | now | 1 day |
    | recovery_mode_clean_expired_keys | 2021-01-09 04:58:33 | now | 1 day |
    | wpseo_home_url_check | 2021-01-09 04:58:36 | now | 1 day |
    | flamingo_daily_cron_job | 2021-01-09 04:58:36 | now | 1 day |
    | wp_scheduled_auto_draft_delete | 2021-01-09 09:34:33 | now | 1 day |
    | wpseo-reindex | 2021-01-09 09:51:33 | now | 1 day |
    | wp_scheduled_delete | 2021-01-09 10:05:30 | now | 1 day |
    | delete_expired_transients | 2021-01-09 10:05:30 | now | 1 day |
    | wp_site_health_scheduled_check | 2021-01-10 04:58:35 | now | 1 week |
    | wpseo_ryte_fetch | 2021-01-13 18:07:41 | 2 days 8 hours | 1 week |
    +------------------------------------+---------------------+-------------------+------------+

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_privacy_delete_old_export_files
    Executed the cron event 'wp_privacy_delete_old_export_files' in 0.018s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_version_check
    Executed the cron event 'wp_version_check' in 1.93s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp_update_plugins
    bash: wp_update_plugins: command not found

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_update_plugins
    Executed the cron event 'wp_update_plugins' in 0.048s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wpseo_permalink_structure_check
    Executed the cron event 'wpseo_permalink_structure_check' in 0.008s.
    Success: Executed a total of 1 cron event.

    Executed the cron event 'sucuriscan_scheduled_scan' in 128.4s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_update_themes
    Executed the cron event 'wp_update_themes' in 0.052s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run mwp_update_public_keys
    Executed the cron event 'mwp_update_public_keys' in 0.054s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run recovery_mode_clean_expired_keys
    Executed the cron event 'recovery_mode_clean_expired_keys' in 0.005s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wpseo_home_url_check
    Executed the cron event 'wpseo_home_url_check' in 0.006s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run flamingo_daily_cron_job
    Executed the cron event 'flamingo_daily_cron_job' in 1.607s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_scheduled_auto_draft_delete
    Executed the cron event 'wp_scheduled_auto_draft_delete' in 0.006s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wpseo-reindex
    Executed the cron event 'wpseo-reindex' in 0.005s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_scheduled_delete
    Executed the cron event 'wp_scheduled_delete' in 0.011s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run delete_expired_transients
    Executed the cron event 'delete_expired_transients' in 0.009s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wp_site_health_scheduled_check
    Executed the cron event 'wp_site_health_scheduled_check' in 4.571s.
    Success: Executed a total of 1 cron event.

    [REDACTED@n3nlwpsftp002 html]$ wp cron event run wpseo_ryte_fetch
    Executed the cron event 'wpseo_ryte_fetch' in 2.595s.
    Success: Executed a total of 1 cron event.

    Mark0514
    New

    I have been having the same issue since approximately the same time. Chat and phone support search their database and tell me Cron jobs are not supported in Managed Wordpress and that I should consider Linux hosting. These are core functions that use WP-Cron and they should be working. They did work until December. They "elevated" my ticket and transferred me, placing me on hold for an hour before I got disgusted and hung up. Seriously considering just finding another host.

    ablake
    Community Manager

    Hi @finiterex,

     

    Your issue is likely related to a filer issue we had recently on the Managed WordPress servers. We had to do some rebalancing to address that issue, and we turned off crons on all Managed WordPress plans except for the Ecommerce tier. If you are using any of the other tiers, that would have affected you.

     

    Fortunately, balancing is done, and we're re-enabling crons for all tiers soon. I don't have an exact ETA, but it's approved for development.

     

    If your cronjobs were running fine before this, things should go back to normal once that's finished. 

     

     

    Angela B - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.

    Unfortunately, none of the 5 tech people I spoke with knew this and they all just kept saying cron wasnt supported in managed wordpress. I eventually paid to have two sites migrated to a cpanel account and I'm still trying to get the second one online.

    Hi,

    I'm afraid I no longer believe anything GoDaddy personnel tell me; I've had 3 different explanations as to what is happening, none of which have made any technical sense nor contained any technical detail that would allow this understanding to be conveyed.  None of the technical support personnel I have spoken to (at least 3, may be 4 by now) had any knowledge of a "filer issue", but one was certainly happy to tell me that "WP_Cron will never work reliably on our managed WordPress because of the load balancing and caching we use"... awesome... good to know before you purchase a service.

    So still no detail of why this is broken and still no resolution or sign of it ever being fixed.  I personally will not be putting any other customers on your platform.

    ablake
    Community Manager

    Hey @finiterex and @Mark0514,

     

    Yeah, I can definitely understand the frustration of getting different & incorrect explanations from support.

     

    The truth is, support representatives don't have level of access and knowledge equivalent to developers and admins - if they did, they probably wouldn't work in support. They do their best with the product knowledge, information, and tools that are available to them. And they can't share too much information about internal systems for security reasons, so they can't always give much technical detail. Saying that it was a filer issues is about as detailed as I can get.

     

    However, we do try to improve the speed and quality of information passed between our developers and support. We use these community posts to track down breaks in communication and improve our processes. So, I appreciate you taking the time to post it here so we can work to do better in the future.

     

     

     

    Angela B - GoDaddy | Community Manager | 24/7 support available at x.co/247support | Remember to choose a solution and give kudos.

    Sorry but that is the biggest load of old tosh!


    There's been this thing called ITIL around since the 1970s and it has a very simple concept of Incident Management leading into Problem Management with one of the key tenants being ensuring that all levels of support are aware of Known Errors (Problem Management) such that the customer can be made aware of any workarounds for Incidents relating to the root cause of a Problem (the definition of a Known Error)... maybe GoDaddy should invest some of it's marketing budget into ITSM implementation and training?

     

    So explaining-away GoDaddy's inability to operate it's services effectively by saying that "support wouldn't be support if they knew what was going on" is completely counterintuitive and in fact just downright wrong... oh and not to mention makes a mockery of your customer base (apparently we're not idiots!).

     

    So... how about someone with some actual knowledge and seniority in GoDaddy pops along to this public forum and provides some actual explanation for why you are:

     

    1. Possibly misrepresenting / misselling a service

    2. Unable to provide consistent and informed support to your paying customers

    3. Leaving your customers with a broken service.

     

    There's some wonderful legislation called the trade descriptions act that comes to mind.