Summary

After cloning servers, some configurations that were previously managed in the Ploi panel (notably cronjobs and redirects) disappear from the panel UI. However, the underlying config still exists on the server and is only visible/editable via SSH (e.g., cron definitions and Nginx redirect files).

Expected behavior

Cloned servers should retain (or restore) all Ploi panel-managed items so they remain visible and manageable in the UI after cloning.

Actual behavior

• Cronjobs still exist on the server, but do not appear in the Ploi cronjobs panel.
• Redirects still exist in the Nginx config/redirects directory, but do not appear in the Ploi redirects panel.

Hypothesis / likely cause

The clone process appears to copy the server’s configuration files, but does not copy (or re-link) the associated Ploi database records that power the panel UI. Result: “orphaned” configurations—present in files, missing from the panel.

Impact

For users with many existing configurations (hundreds of redirects/cronjobs), this creates major maintenance issues and risks inconsistencies between what’s deployed and what’s visible/manageable in Ploi.

Request / proposed solution (with backwards compatibility)

1. Backfill/re-sync for already-cloned servers: Provide a way for existing cloned servers/sites to re-sync/import cronjobs and redirects so they re-appear in the panel without manual re-creation.
2. Fix for new clones: Ensure that on new server clones, the Ploi panel data for cronjobs and redirects is transferred (or reconstructed) alongside the config files, so the UI remains accurate immediately after cloning.