Restoring Sites = Cron Jobs Vanish — 30 Domains, 0 CRONs, 90 Clicks Later. Why?

Support and Discussion General Discussion
1

Just migrated 30 sites from one CyberPanel server to another — and like usual the cron jobs for every site were NOT restored.

Let me say that again for impact:

When restoring sites from backup, all scheduled cron jobs are lost.

And to make it worse: the UI flow for re-adding them manually is absolutely brutal. Here’s the current process — and you have to repeat this 30 times if you have 30 domains:

:repeat_button: Current Cron Job Navigation Hell

  1. Go to: :8090/websites/listWebsites
  2. Click “Manage” on the domain (no right-click support)
  3. Go to: :8090/websites/domain.tld/
  4. Click through to: :8090/websites/listCron?domain=domain.tld/

Repeat that every single time — no shortcuts, no multi-tab support, no global cron view, no batch import, nothing.

:fire: Why This Is a Dealbreaker

  • Cron jobs are essential to automation — backups, queues, scripts, SEO crawlers, etc.
  • Losing them breaks functionality silently unless you manually check.
  • And re-adding them through this UI? That’s 90+ clicks for 30 sites. That’s laughable in 2025.

:light_bulb: What Needs to Be Fixed — Immediately

  • :white_check_mark: Cron jobs should be included in site backup/restore
  • :white_check_mark: Add global “All Cron Jobs” view across all sites
  • :white_check_mark: Allow right-click + open in new tab on “Manage”
  • :white_check_mark: Allow bulk import/export of cron jobs
  • :white_check_mark: At minimum, let us clone crons from one domain to another

:backhand_index_pointing_down: Who Else Has Been Burned by This?

If you’ve hit the same wall, drop a comment. Let’s make sure the devs prioritize real-world admin use cases — not just gradients and buttons.

This isn’t a niche edge case — it’s core automation being silently dropped during migration. That’s a big deal.

2 Likes