SSH developer access
Account SSH keys, which servers they can reach, and short-lived tokens for connecting to one.
Reaching a Xuda-managed server over SSH has three layers: the keys your account owns, which of them a given server accepts, and a short-lived, revocable token that actually opens the connection. Every connection tunnels through Xuda; nothing here hands you the server's own address directly.
Add a key to your account
Settings > Security > SSH keys holds every public key your account can offer to a server. Each key is one line: its name, the type and end of the key, when it was added, how many servers it opens, and one status: On, Off, Expiring soon, Expired or No server.
Generate a key pair, if you do not already have one
Accept the default file location and, optionally, set a passphrase. This creates two files: a private key you keep, and a .pub file you share.
Add the public key
Press Add SSH key (an account with no keys opens the form straight away). In the New SSH key form, paste the contents of the .pub file into SSH key content, give it a Key name, and press Add key. The key is checked as you paste it, so a private key, a line that is not a public key, or a comment without an @ is named before you add anything. An Expiry date (optional) can be today or later; leave it empty for a key that never expires. The new key then opens in place, marked No server: nobody can use it until you choose its servers (see the next section).
Manage a key
Press any key's row to open it in place; one key is open at a time. The open key shows its status, the key with its expiry date, and the days left until that date. A key that needs you opens by itself: one that has expired but is still on a server, otherwise the one on a server that expires soonest inside 14 days. In the open key:
- Edit changes the key's name and expiry date. The key itself is read only: to change it, add a new key. On a key marked Expiring soon the button reads Extend expiry, and on an expired key Set a new expiry; both are the same edit, opened on the date. Clear beside the date removes the expiry.
- The Access switch turns the key off without deleting it, which takes it off every server it is installed on at once. A server that cannot be reached keeps the key on, and the line under the switch says how many servers did not answer, so you can try again. Turning a key back on does not reinstall it: add it again on each server.
- Delete asks you to confirm, then takes the key off every server it opens and deletes it. If a server does not answer, the key is not deleted.
The Access log, the last row under your keys, opens in place and lists every grant, removal and expiry on the account, newest first: six events, then Show all for the rest (the latest 500 in all). Activity for this key, in an open key, opens the same log for that one key, and All keys widens it back to the account.
A key inside 14 days of its expiry date shows Expiring soon while it is on a server; past the date it shows Expired. Before its date passes, a key that is off shows Off and one on no server shows No server. Expired keys come off their servers once an hour; turn an expired key off to take it off now. Once it is off its servers it has no switch: give it a new date with Set a new expiry, then add it on a server again. An expired or off key cannot be newly assigned to a server, but removing one already assigned still works.
Choose which server a key can reach
Adding a key to your account does not by itself give it access to anything, and the key's own screen shows how many servers it opens, not which ones. Open a VPS, managed VPS, datacenter or deployment's Advanced tab and press Assign keys, on the SSH keys row under Keep it current, to pick which of your account's keys may reach that particular server.
Saving reconciles your selection against what was installed when you opened the picker: newly checked keys are installed first, then unchecked ones are removed, so a key the server refuses (because it is off or expired) can never strip access that was already working. An off or expired key is shown as such in the picker and cannot be newly selected.
Connect to the server
Open the project and press Connect on its SSH securely row (VPS-family projects only) to open Developer access, a manager for named, revocable connection tokens, separate from the account keys above.
Create a named access
Press Add access, give it a label (who or what it is for) and, optionally, an expiry (7, 30, 90 or 365 days, or never). Creating it shows a one-time connection token: copy it now, it cannot be shown again.
Install the client and connect
The dialog gives a copy-paste install command and a connect command per platform (macOS, Linux, Windows), built around websocat, which tunnels the connection to a port on your own machine. Point any SSH or SFTP client at that local address once the tunnel is running, signing in as root.
Manage it afterward
Each named access has its own suspend switch; suspending, letting an expiry pass, or deleting an access is enforced at the tunnel itself, closing a session already in progress. Regenerate mints a fresh token for an existing access and invalidates the old one; it never rotates automatically, since that would cut off anyone still using it. Deleting an access asks for confirmation first.
A connect attempt fails with this error when no account key has been assigned to that server yet. Add a key under Settings > Security > SSH keys, then assign it to the server, before trying again.