Title: cron issue
Last modified: August 30, 2016

---

# cron issue

 *  Resolved [Antonio D.](https://wordpress.org/support/users/colomet/)
 * (@colomet)
 * [11 years ago](https://wordpress.org/support/topic/cron-issue-1/)
 * i have the backupwordpress in several sites.
 * I change the domain name of my sites from one company to a other, then the server
   company did make the DNS configuration. Can be that the reason why in 2 multisite
   installations from one domain name i get that problem
 * BackUpWordPress ha detectado un problema. wp-cron.php is returning a 301 Moved
   Permanently response which could mean cron jobs aren’t getting fired properly.
   BackUpWordPress relies on wp-cron to run scheduled backups. See the FAQ for more
   details.
 * Also i can not do manual backups.
 * reading te faq, i did that (following line) and the message disappear, but i 
   can not make the backups anyway.
    * Try adding `define( 'ALTERNATE_WP_CRON', 
   true );` to your `wp-config.php`, do automatic backups work?
 * [https://wordpress.org/plugins/backupwordpress/](https://wordpress.org/plugins/backupwordpress/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [Antonio D.](https://wordpress.org/support/users/colomet/)
 * (@colomet)
 * [11 years ago](https://wordpress.org/support/topic/cron-issue-1/#post-6241240)
 * looks like we fix it.
 *  [J.D. Grimes](https://wordpress.org/support/users/jdgrimes/)
 * (@jdgrimes)
 * [10 years, 5 months ago](https://wordpress.org/support/topic/cron-issue-1/#post-6241500)
 * In case anybody else has this same problem:
 * I was getting this same message. The site was using CloudFlare and flexible SSL.
   I had added a page rule like this to force the site to use SSL:
 *     ```
       http://*example.com/*
        Always use https
       ```
   
 * The fix for me was adding a new rule with a higher priority to allow access to`
   wp-cron.php` over non-SSL connections (I think that somehow the site isn’t quite
   configured properly for SSL, and BackUpWordPress’s requests were being made using
   HTTP instead of HTTPS):
 *     ```
       *example.com/wp-cron.php*
       SSL: Off
       ```
   
 * This fixed the issue, and I didn’t need to add `define( 'ALTERNATE_WP_CRON', 
   true );` to the `wp-config.php`.
 * If you are having similar trouble, do check if you can actually access `example.
   com/wp-cron.php`, in my case my browser told me that it wasn’t redirecting properly.
   After adding that second page rule in Cloudflare, I was able to access `wp-cron.
   php` on my site.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘cron issue’ is closed to new replies.

 * ![](https://ps.w.org/backupwordpress/assets/icon-256x256.jpg?rev=1105225)
 * [BackUpWordPress](https://wordpress.org/plugins/backupwordpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/backupwordpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/backupwordpress/)
 * [Active Topics](https://wordpress.org/support/plugin/backupwordpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/backupwordpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/backupwordpress/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [J.D. Grimes](https://wordpress.org/support/users/jdgrimes/)
 * Last activity: [10 years, 5 months ago](https://wordpress.org/support/topic/cron-issue-1/#post-6241500)
 * Status: resolved