Rename, resize, delete or forget a server

A server's life does not end when you stop needing it, and it does not always stay the same while you use it. You might rename it, move it to another organisation, take it out of SrvYard while the machine keeps running, or delete it for good. This article explains each option, what it does to the machine and to the sites on it, and which ones can be undone.

The short version: rename and settings are safe and reversible; archive is reversible and never touches the machine; transfer moves everything to another organisation you own; delete removes the server from SrvYard and, for cloud servers, lets you decide whether the machine is destroyed as well.

Before you begin#

• A role that may do it. Archive, transfer and delete each have their own permission, and the Danger card shows only the actions you may use.
• A ready (or disconnected) server for archive, and a server that is not busy (installing, rebooting) for transfer and delete.
• A backup of anything you need. Delete is permanent for the SrvYard record, and for a cloud server it can destroy the machine and its data.

1. Rename a server or change its address#

Names, notes, timezone and the address of a machine you connected yourself are on the Overview tab, in the Settings card (see Read the server overview). Change the Name (up to 60 characters) and press Save changes. The server's login banner is refreshed after a rename. The Handle, a lowercase identifier unique among your servers, is edited in the Identity card next to it.

For a Custom VPS you can also change the IP address and SSH port there. Changing the address of a ready server re-verifies the connection, and the fields are disabled while the server is busy. A cloud server's address is assigned by the provider, so it cannot be edited.

2. The Settings tab#

The Settings tab is not about the name: its description says it holds the generated credentials, the private network of this server, Redis, and what happens when you no longer need it.

1. Server credentials. SrvYard sets a sudo password for the management user and a database administrator password (srvyard_admin, the root password) for every database engine. You get them once, as a download, and they are not stored, so keep the file in a password manager. Generate credentials creates them for a server that has none (the badge says Not generated); a download link then waits for a limited time before it is destroyed.
2. Private IP address. The address of this server inside the provider's private network. Peers connect to it, and SrvYard uses it to build firewall rules.

1. Allow access. Lets another server on the same provider connection and region reach this one, for example a web server reaching a database server. SrvYard opens the matching firewall rule.
2. Remove access. Closes it again. The entry shows the port that was opened (here 3306).
3. Change password (Redis). Sets or removes a password for the Redis on this machine. It listens on localhost only; the password is a second lock. Reveal shows it and the view is recorded in the audit log.

Below those cards is the Login banner: the text people see when they sign in over SSH. Install banner replaces Ubuntu's welcome messages with the server's name, health, sites and services. The stock scripts are switched off, never deleted, so restoring brings back exactly what Ubuntu shipped.

3. The Danger card#

At the bottom of the Settings tab, Danger collects the actions that stop a server.

1. Archive server. Reversible. The machine keeps running.
2. Transfer server. Moves it to another organisation you own.
3. Delete server. Removes it from SrvYard.

All three also appear in the Actions menu in the header of every server page.

4. Archive: forget it for now#

1. Type the server's name to confirm. The button stays disabled until it matches.
2. What it does. SrvYard stops monitoring and managing the server. The machine keeps running and its provider keeps billing you. Only a ready or disconnected server can be archived.

An archived server drops out of the server list (filter by Archived status to see it) and does not count towards your plan's server limit. To bring it back, choose Unarchive: SrvYard reconnects with the key it left on the machine and checks the connection. If the key was removed, run the reconnect command shown on the page from the provider's console. Unarchiving needs room in your plan.

5. Transfer: move it to another organisation#

1. Organization. The destination. You can only move a server between organisations you own; if you own no other, create one first.
2. What stays behind. Tags, team access, saved Git connections, library SSH keys and backup configurations stay in the old organisation (the archives stay in your storage). A cloud machine stays in your provider account, so the new organisation cannot delete it at the provider.

Type the name to confirm. The destination must have room for the server and its sites in its plan, otherwise the transfer is refused with a plan-limit message.

6. Delete: remove it from SrvYard#

1. Preserve this server at the provider. On by default for cloud servers. When on, the server is only removed from SrvYard and keeps billing you at the provider. Turn it off and the machine is destroyed at the provider with all its data. This cannot be undone.
2. Type the server's name to confirm.

For a Custom VPS the dialog says the server is removed from SrvYard only and the machine itself is not touched. In every case the server's sites are forgotten with it: their free subdomains are released, and their domains, certificates, processes and scheduled jobs are deleted from SrvYard. Credentials waiting for download are destroyed. SrvYard confirms with a message: either that the server was deleted, or that it was removed from SrvYard and the machine was not touched.

Troubleshooting#

• The archive, transfer or delete button is disabled. The server is busy (installing, rebooting, being deleted) or, for archive, not ready or disconnected. Wait for the operation to finish.
• "The provider could not delete the machine". The provider refused. SrvYard keeps the server record so you can retry; check the provider's console or turn Preserve on and delete the machine there yourself.
• "SrvYard has no connection to the provider of this machine any more". The provider connection was removed. Keep the server at the provider (switch Preserve on) and delete it there.
• Transfer is refused with a plan limit. The destination organisation has no room for another server or for its sites. Upgrade it or free capacity first.
• I archived the wrong server. Use Unarchive from the server's page; it reconnects and checks the connection.
• The credentials link expired. Generated credentials are available for one download for a limited time. Generate new ones, which sets new passwords.

Related#

• Read the server overview: where the name and notes are edited.
• Add a server provider and its API token: you cannot remove a provider while it has servers.
• Create, rename and switch organisations: the organisation you transfer to.
• Cancel, export data and delete the organisation: when you stop using SrvYard altogether.