Why is my published site offline?

A published TeleportHQ site goes offline for one of a few reasons: someone clicked Unpublish site in the Publish window, the workspace's trial or subscription ended (TeleportHQ then removes every deployment and custom domain), a web app passed its 7-day window without a Web App slot, your custom domain's DNS doesn't point to TeleportHQ, or the project was deleted. The Publish window and the project's card on your dashboard tell you which one.

First, check your dashboard and the Publish window#

These two TeleportHQ checks take a minute and point you to the right cause:

1. On your dashboard, find the project's card. A live site shows its address under the project name. Not deployed means the site isn't live. A card can still show an address while the site is offline, for example a custom domain or the address of an archived project, so click the address to check.

2. Open the project in the editor. At the top right, click Publish.
3. In the window's left menu, keep Publish selected. At the top, keep Production selected.
4. Look at the status at the right of your TeleportHQ address, right below Production: Published, Unpublished, Publish failed or Publish in progress.

Then find the cause below that matches what you see.

1. Someone clicked Unpublish site#

How to tell: in the Publish window, your TeleportHQ address shows Unpublished and is no longer a link. The red Unpublish site button at the bottom left of the window is gone, but Deployments still lists your earlier Production deployments. Your staging address, if you have one, still works.

Cause: someone with the Owner, Admin or Designer role clicked Unpublish site at the bottom left of the Publish window and confirmed in the Unpublish your site window. TeleportHQ then stops serving the site at your TeleportHQ address and at your custom domain. The project, its deployments, its staging site and the custom domain connection all stay.

Fix: publish the site again.

1. In the editor, at the top right, click Publish. Keep Production selected.
2. If your site has a custom domain, keep Publish to custom domain ticked at the bottom of the window.
3. Click Publish to Production.

You can also bring back a version you already built: in Publish → Deployments, click Redeploy on a Production deployment. See How to take your site offline (Unpublish).

2. The trial or subscription ended#

How to tell: the workspace owner's dashboard shows Your trial has ended or Your subscription has ended, with "Deployments and custom domains have been removed and your projects are archived." Other members see This workspace is locked. Project cards show Archived.

Cause: when a TeleportHQ trial or subscription ends, TeleportHQ takes down the published site of every project in the workspace, removes their custom domains from hosting, and archives the projects. After a trial that ended without a subscription, the panel also tells you when the archived projects will be permanently deleted, for example "They will be permanently deleted in 12 days." That happens 30 days after they were archived. After a paid subscription ends, the projects are kept and never deleted.

Fix:

1. The workspace owner clicks Subscribe to restore access (or Renew to restore access) and subscribes. See How to subscribe to Pro or Premium.
2. The projects come back, with the message "Welcome back! Your projects have been restored. Re-deploy to take your sites live again."
3. Open each project and click Publish to Production. See How to publish your site.
4. Open your custom domain in a private browser window. If it doesn't show your site, see Why is my custom domain not working?.

A failed card payment doesn't take the site down straight away: the workspace keeps access while the payment is retried, for up to 21 days. See My payment failed: how do I update my card? and What happens when my trial or subscription ends?.

3. A web app ran out of its 7-day window#

How to tell: the project's card shows a red Subscription required chip and the line "Archived until a slot covers it". Point at the chip to read "This web app needs a slot to come back online." Before that, during the 7 days, the chip was amber and the line read "Site goes offline in N days" with the date, and the editor showed a banner: "This web app has full access — including publishing with a TeleportHQ watermark — but needs its own subscription to keep it."

Cause: a TeleportHQ web app that isn't covered by a Web App slot gets 7 days of full access. After that, its site goes offline and the project is archived until a slot covers it. Subscribing the workspace again doesn't bring it back: only a Web App slot does.

Fix: assign a Web App slot to the project, or buy one, then publish it again. See How to buy, assign or cancel a web app slot and Why does my web app need a slot, and what is the 7-day window?.

4. Only your custom domain is down#

How to tell: your teleporthq.app or teleporthq.site address opens the site, but your own domain doesn't.

Fix: check the DNS records at your domain provider, and the domain's status in the Publish window. See Why is my custom domain not working?.

5. The site was never published to Production#

How to tell: your TeleportHQ address in the Publish window shows Unpublished, and Deployments lists no Production deployment. You may have published only to Staging.

Fix: click Publish to Production. A staging address is a private test copy, not your live site. See How to publish your site and How to test changes on a staging site before going live.

6. The last publish failed#

How to tell: the status at the right of your address says Publish failed.

Cause and fix: a failed publish leaves the version that was already live as it is. If the site was never published before, nothing is online yet. Find the message you saw in Publishing failed: what should I do?.

7. Only one page shows "page not found"#

How to tell: the site opens, but one address shows a "page not found" page.

Cause: the page was deleted or its address changed, the page is kept out of the published site, its AI generation failed, or a button or link points to an address your site doesn't have.

Fix:

• At the top left of the editor, click the yellow issues chip if you see one. The Issues window lists every link that leads nowhere, under Broken links on pages. See How to find and fix broken links on your site and What do the warnings at the top of the editor mean?.
• Check that the page isn't excluded. See How to keep a page out of your published site.
• Check the page's address. See How to change a page's URL and create nested URLs.
• Publish again after each fix.

8. Visitors see a password page, not the site#

Cause: Password Protection is on for the site. Either the workspace has no paid subscription, for example it's on the trial, and then every publish is password-protected, or someone clicked Enable on Pro or Premium.

Fix: in Publish → Production, open the Password Protection option below the Custom domain section, copy the password and share it, or click Remove there on Pro or Premium. Without a paid subscription, the password stays until the workspace subscribes. See Why does my published site ask for a password?.

9. A link you shared during the trial no longer opens the site#

How to tell: the workspace subscribed after you published on the trial, and the link you shared ends in .teleporthq.app.

Cause: TeleportHQ trial sites are published on a .teleporthq.app address. After the workspace subscribes, the next publish moves the site to a .teleporthq.site address.

Fix: in the Publish window, copy your TeleportHQ address (right below Production) and share it again.

10. The project, workspace or account was deleted#

Cause: deleting a project, a workspace or the owner's account takes its published sites offline and frees their addresses. A deleted project can't be restored from the app.

Fix: if you have a copy of the project, publish the copy. For help, write to the TeleportHQ team at hello@teleporthq.io.

Not a cause: "Show this site in search engines"#

Turning off Show this site in search engines in Project settings (cog, bottom left) → SEO & social → Search engines doesn't take your TeleportHQ site offline. Your site keeps working for everyone who has the address. From your next publish, it only asks search engines not to list it, and the Publish window says "Hidden from search engines. Every address of this site asks them not to list it; change it in Project Settings › SEO." If your site disappeared from Google but opens fine, turn the switch back on and publish again. See How to hide a page from Google, set a canonical URL or redirect a page.