How to see and manage your deployments
Every time you publish a TeleportHQ project, a new deployment (one built version of your site) is created. To see them, click Publish at the top right of the editor, then click Deployments on the left of the Publish window. Each row shows the address, date, status and whether it's Production or Staging. The ⋮ button on each row opens a menu with Redeploy, Promote to Production, Build Logs and Delete.
Before you start
- Publish at least once. Until then, the list says "No available deployments". See How to publish your site.
- Plan. Publishing needs a Trial, Pro or Premium workspace.
- Role. You need the Owner, Admin or Designer role. With another role, clicking Publish shows "Your current role does not have enough permissions to publish this project".
Steps
- Open your project in the editor.
- At the top right, click Publish. The Publish window opens on the Publish tab.
- In the Publish window, click Deployments on the left. The list "A list of all your Vercel deployments" appears, newest first.
- To see older deployments, click Load more at the bottom. The list loads 8 deployments at a time. When there are no more, you see "All data loaded".
- To act on a deployment, click the ⋮ button at the end of its row, then click an action in the menu.
What each row shows
In the TeleportHQ Deployments list, each row describes one deployment:
- The address and the date. Click the address to open that version. The deployment your live site serves shows your TeleportHQ address, or your custom domain followed by a +1 chip that opens the TeleportHQ address. Older deployments show their own unique link. Under the address is the date and time of the publish. When you point at the address, a copy button appears: it copies that deployment's own unique link.
- The status, such as Ready, Building, Queued, Error or Canceled.
- The environment: Production (your live site) or Staging (your private test address).
- The ⋮ button, which opens the actions. While an action runs on that deployment, a spinner replaces it.
What each action does
| Action | What it does |
|---|---|
| Redeploy | Builds that deployment again, in its own environment, and puts it back on that environment's addresses. You see "Deployment successfully redeployed. You can check it out in the Deployments tab." Redeploying an older Production deployment puts that version back on your live site: see How to go back to an earlier version. |
| Promote to Production | Makes a finished Staging deployment your live site, without rebuilding. You see "Your live site now serves the build you tested. Nothing was rebuilt, so it is exactly what you checked." It's greyed out for Production deployments and for staging builds that aren't Ready yet. |
| Build Logs | Opens the build log under the row, to see what happened during the build. See How to read build logs. |
| Delete | Removes the deployment. You see "Deployment deleted successfully". It's greyed out for the deployment that serves your custom domain, and when it's the only deployment in the list. |
Redeploy, Promote to Production and Delete are also greyed out while a publish is running. Build Logs always works.
Troubleshooting
"Deployment could not be deleted. Error message: Could not redeploy deployment…" after clicking Redeploy The redeploy failed, even though the message says "deleted". Try again. If the message appeared after about two minutes of waiting, the build may still finish by itself: check the list again in a few minutes before you retry.
"Deployment could not be deleted. Error message: Could not delete deployment…" after clicking Delete TeleportHQ never deletes a project's last deployment, or the deployment your custom domain serves. Publish a newer version first. For any other deployment, try again.
"Deployment could not be promoted to production. Error message: …" Wait until the staging deployment shows Ready, then try again. If the message includes "This deployment is not finished building yet, so it cannot be made live", the staging build is still running.
The ⋮ menu options are greyed out Another publish is running. Wait until it finishes.
The list says "No available deployments" although you published before Close the Publish window and open Deployments again: the list may not have loaded. If it's still empty, the deployments may have been removed because the trial or subscription ended (see below).
Good to know
- TeleportHQ hosting runs on Vercel. That's why the list says "A list of all your Vercel deployments". You don't need a Vercel account of your own.
- Deployments are removed when a plan ends. When the trial or the subscription ends, TeleportHQ deletes all of the project's deployments and the site goes offline. See What happens when my trial or subscription ends?.
- Deleting the deployment your live address serves. If your site has no custom domain, you can delete the deployment your TeleportHQ address serves. The newest earlier Production deployment that finished building then takes over that address. If you delete the deployment that serves your staging address, the staging address stays empty until your next staging publish.
- Unpublish keeps your deployments. When you take your site offline with Unpublish site (at the bottom left of the Publish window, on Production), every deployment stays in this list, and opening the list doesn't put the site back online. Redeploy on a Production deployment, or Promote to Production on a staging one, brings it back. See How to take your site offline (Unpublish).
- Staging is a separate environment, with its own address. See How to test changes on a staging site.
- Deployment links can be protected with a password. See How to password-protect your site.