For a hosting workflow with a separate Publish action, a saved project and a successfully published website are separate states. Preserve the project while investigating a publication error.
Steps
- Record the project, target domain, time, and exact publication message. Check whether a publication task is still active before retrying.
- Confirm that the destination is the intended website and that you have a recoverable copy of existing content before its first Sitejet publication.
- For a storage warning, inspect account usage and safely remove only identified, expendable files. cPanel documents that an account over quota cannot publish.
- For an unavailable target, inspect the domain’s eligibility and document root in the panel. A working editor preview does not prove that the hosting destination is ready.
- Correct the reported cause, publish once, and check the resulting status. If publication succeeds but visitors still see the old page, follow the separate stale-content checks.
Check the result
Open the public HTTPS address outside the editor and inspect a page changed in this publication. Confirm that existing downloads and forms still work.
Before you continue
Keep backup archives outside the public site. Do not repeatedly empty the document root or manually edit generated files to force publication.
Documentation for this guidance: docs.cpanel.net — sitejet builder.
