Fixes for common problems that affect your whole project.
A TeleportHQ project opens read-only when your role only allows viewing, the workspace's trial or subscription has ended, you opened a public or cloneable link, the editor lost its connection, or a teammate is editing the same element; the message you see tells you which, and each case has its own fix.
In TeleportHQ, you can't create a project when the workspace is at its project limit (a trial workspace holds 1 project, archived ones included), its trial or subscription has ended, your role or folder access doesn't allow it, or a template or AI token limit applies; the message on screen names the cause, and each has a fix.
A published TeleportHQ site goes offline when someone clicks Unpublish site in the Publish window, the workspace's trial or subscription ends (TeleportHQ then removes every deployment and custom domain), a web app passes its 7-day window without a Web App slot, the custom domain's DNS isn't set up, or the project is deleted; the Publish window and the dashboard card show which one.
TeleportHQ doesn't publish design and page changes by itself, so they reach your live site only after you click Publish to Production; blog posts, help center articles and database records go live without a publish, usually within seconds, while cached lists and API answers can lag until their cache time runs out (5 minutes by default).
When publishing a TeleportHQ site fails, the message names the reason - a build error (read the Build Logs in the Deployments tab), a page, component or style the code can't use, a plan limit such as forms, language slots or a Web App slot, a workflow security problem, private files, or a temporary error you can retry - and your live site stays as it was.
When the TeleportHQ editor loses its live connection it shows "Connection lost. Reconnecting automatically… Your edits are paused until it is back." (or "You're offline…") and pauses editing until it reconnects by itself; other messages warn about a small window, an unsupported browser, a phone or touch screen, or too many people in the project, and reloading or using a Chromium-based browser fixes most cases.
A TeleportHQ site asks for a password when its workspace has no paid subscription, because then every publish, on the trial for example, is password-protected, or when someone clicked Enable under Password Protection on Pro or Premium; copy the password from Publish → Production → Password Protection, and subscribe or click Remove there to make the site public.
