Troubleshooting
Diagnose managed OrbitPage sign-in, save, publication, upload, domain and integration problems without losing unsaved work.
Last reviewed 15 October 2026Start with the selected workspace, account role and exact action that failed. Keep a copy of unsaved text and the visible error before refreshing. Compare the editor with the public page to distinguish editing from publication problems.
Cannot sign in or open a workspace
Use the original email/password or Google identity. Complete verification or the two-factor challenge shown. If sign-in succeeds but the workspace is missing, check the invited email and active membership with its owner. A missing role or plan entitlement is not fixed by clearing browser storage.
Save failed or changes are not public
Save the section you edited; another section's Save does not include it. Check field validation, role permissions, plan limits and any moderation notice. If another session changed the page, preserve your intended edit, reload the current version and apply it again instead of overwriting an old revision.
A publication failure can leave the previous valid public version online. Inspect the dashboard message, retry after resolving the cause and open the exact public address. Check publication controls for Menu, Shop and subpages, and explicit draft publication in API or ChatGPT workflows.
Media upload or storage error
Check the accepted file type, per-file size and remaining workspace storage. A filename extension alone does not establish a valid media type. Keep the original file and existing working asset until the replacement succeeds. Review unused media before cleanup and export first if older content may depend on it.
Custom domain is pending or points elsewhere
Check the exact CNAME, ownership TXT and certificate TXT values shown in Plan. Leave proxying disabled until activation, remove conflicting routing records only after checking their purpose, and allow propagation. Use Check now and read the status. Only an active HTTPS connection is ready to share.
Email, payments or embeds fail
For email, test the correct Shop or Newsletter sender and inspect provider delivery logs. For payments, check Stripe readiness, Compliance, publication and order status. Do not repeat a live purchase or send merely to clear an error. For embeds, check the supported public URL and consent category in a fresh session.
Report an unresolved problem
Send the public page URL, approximate time and timezone, browser, action, visible error and whether the issue affects the editor or visitors. Include a sanitized screenshot if helpful. Keep passwords, tokens, recovery codes, buyer details and signed delivery links out of the report. SaaS users do not need to run server commands or edit a database.