Skip to content
Hyperion

Suspend, resume or delete a website

Suspending a hosting keeps everything and serves a 503 page. Deleting removes it, either immediately or through Trash, depending on a setting.

Before you start

Section titled “Before you start”
  • Suspend and resume need the Suspend / resume permission. Delete needs Delete hostings.
  • Decide whether Trash should be on. It is off by default, which makes every delete immediate and permanent. See the last section.

Steps

Section titled “Steps”

Suspend and resume

Section titled “Suspend and resume”
  1. Open Hostings and click the site.
  2. Click Suspend in the top bar, optionally confirm, and wait for the state pill to read suspended.
  3. To bring it back, click Resume in the same place.

Suspending serves an HTTP 503 page, stops PHP-FPM, locks the database user and kills the site’s running processes. Its FTP and SFTP logins stop working. Nothing is deleted. The Danger zone tab offers the same action as Suspend hosting and Resume hosting.

On the Hostings list you can tick several sites and use Suspend, Resume, Back up now or Delete from the bar above the table.

Delete a website

Section titled “Delete a website”
  1. Open the site, then the Danger zone tab. (The Delete button on the Hostings list does the same.)
  2. Optional: tick Keep the Linux user or Keep the database. Either one makes the delete immediate even when Trash is on. If you may run backups, you can also tick Also delete this site’s backups on this node to remove the site’s archives and dumps from this node. This cannot be undone, and without it they stay.
  3. Click Delete hosting.
  4. In the dialog, type the domain. If the site has backups on the off-site FTP target and you may run backups, you can tick Also delete this site’s backups from the off-site FTP target. With Trash on, those copies go when the site leaves the trash. Backups on S3 are not touched.
  5. Click Delete permanently (or Delete with FTP backups).

The delete runs as a background job and opens its page under Background jobs.

Restore or purge from Trash

Section titled “Restore or purge from Trash”
  1. Open Trash in the sidebar. Each row shows the domain, node, when it was deleted and Auto-purge in.
  2. Click Restore to bring the site back online, or Delete permanently to skip the retention window. The second asks you to type the domain and cannot be undone.

If you create a site with the same domain as a trashed one, Hyperion purges the trashed copy first to free the name.

Turn Trash on

Section titled “Turn Trash on”
  1. Open Settings, then Backups, and find Deleted sites.
  2. Tick Move deleted sites to Trash first and set Keep them for (1 to 365 days; the stored default is 30).
  3. Click Save.

A trashed site is offline: nginx answers 503, PHP-FPM stops, and its database and system users are locked. Files, database, certificates and user are kept. On a cluster, a delete runs on the node that owns the site and reads that node’s copy of the setting.

Check that it worked

Section titled “Check that it worked”
  • Suspended: the site’s pill reads suspended and curl -sI https://example.com/ returns HTTP/2 503.
  • Deleted: the job on Background jobs ends successfully, and the site is gone from Hostings. With Trash on it appears in Trash instead.

If it fails

Section titled “If it fails”
  • hosting is suspended — resume first, then change PHP version: some changes need an active site. Resume it first.
  • hosting is already in trash — restore or purge it instead: use Trash.
  • The delete job fails with a message: the hosting stays. Open the job under Background jobs to read it, fix the cause and delete again. When you asked for off-site FTP backups to be deleted and they cannot be, the hosting stays.
Section titled “Related”