Site Repair & Recovery | Domain Command Post

Open the repair workspace

Program path: Operations → Site Repair Center

Select the affected website.
Review the deployment banner. Direct Apply stays blocked until the exact hosting connection, cPanel account/user and document root are confirmed.
Open Issues to review current incidents and the affected URLs.
If source is required, choose Upload Source ZIP. DCP analyzes the archive before a repair plan is built.

Build a repair safely

Create or review the repair plan and changed-file list.
Run Dry Run. DCP checks package integrity, protected paths, database safety, deployment access, live-source drift and restore storage.
For live deployment, DCP captures the exact files that exist immediately before the change and verifies the restore archive.
DCP uploads only the planned changed files to the confirmed destination.
Post-repair validation retests the affected URLs and configured critical pages.

Success looks like: the repair reaches Testing, the site passes validation, and both Keep Changes and Undo Repair remain available until you accept the result.

Undo instead of improvising

If the site does not look right, choose Undo Repair. DCP restores the exact pre-repair files from the verified restore point. A rolled-back repair can be reapplied later from the same protected repair record.

Why Apply may stay disabled

Reason	Meaning
Patch Only	DCP cannot prove a safe live destination yet. Download/use the patch manually.
Mapping incomplete	Hosting was found, but the cPanel user or exact document root is still missing.
Source changed	The live file hashes changed after the source snapshot. Re-analyze instead of overwriting newer work.
No restore storage	No backup means no Apply. Free/assign storage first.

Still stuck?

Write down the edition, program version, the exact path you opened, the last successful step and the full visible error. Do not send product keys, passwords or provider secrets.