Use this workflow when the editor fails to launch, loops back to sign-in, or opens the wrong website.
Steps
- Confirm the hosting account and selected domain. Record the message and whether failure happens before the editor opens or while its canvas loads.
- Save work in any functioning editor tab, sign in to the hosting panel again, and launch Sitejet from that domain’s controls. An old editor URL may depend on an expired session.
- If the browser reports a blocked window, allow the requested editor window for the trusted hosting site. Test a current browser profile without interfering extensions.
- For a domain eligibility message, inspect the panel’s domain configuration. In cPanel, shared document roots and redirects can make a domain unavailable to Sitejet.
- If the editor opens but one page fails, compare another page in the same project. Review recently added embeds or code separately from account access.
Check the result
Open the intended project and verify its save behavior on an unpublished test copy before continuing substantial work. Sitejet Studio can push saved edits directly to an already published site.
Before you continue
Do not delete a domain, remove a redirect, or replace an existing site merely to clear an access error. Those changes can affect working services.
Documentation for this guidance: docs.cpanel.net — sitejet builder; help.sitejet.io — 24275952909463 Overview Website Builder CMS.
