First time here, or this console was put back from a backup (a backup never carries its password or 2FA). Type the one-time setup code, then choose a password for this console. The code is in the console's service log and in the file ops-agent/setup_token on the server.
Scan this with your authenticator app (Google Authenticator, Authy or similar), then sign in.
Cannot scan? Type this key into the app instead:
Measured by the app every minute. A number in red is past its safe line; the reason is written in the Status column.
| CLIENT | STATUS | SIZE | GROWTH A DAY | CONNECTIONS | TRANSACTIONS A SECOND | READS FROM MEMORY | SLOWEST QUERY | OLD ROWS | READINGS A MINUTE | WAITING READINGS | LAST BACKUP | RESTORE CHECK | CHUNKS | CPU / MEMORY |
|---|
The parts of the app running on this server. "View log" shows the last 200 lines as plain text, easy to copy.
| NAME | IMAGE | STATUS |
|---|
Which doors into this server are open. Shown as the server reports it.
Keys that can connect to this server. Removing one takes two steps on purpose: archive first (it stops working at once, nothing is lost), then delete it for good whenever you are sure.
| NAME | FINGERPRINT |
|---|
| NAME | FINGERPRINT |
|---|
Looking only: nothing here can change a record. Each client has a database of its own; "ucaat" is the main one.
The whole server. Open, change, upload, rename, copy and delete. Deleted things go to the Bin below for 7 days first. Every change is written in the change log at the bottom.
| NAME | SIZE | CHANGED |
|---|
Pick a file in the list to read or change it here.
Deleted things wait here for 7 days, then they are removed for good by themselves. The earlier version of a file changed with Save, and anything replaced, waits here too.
| NAME | WHERE IT WAS | WHY | REMOVED | GOES FOR GOOD |
|---|
Every change made from this console's Files, Backups and versions, and Updates pages, newest first: who, when, what, and the internet address it came from.
| WHEN | WHAT | WHERE | WHO | FROM |
|---|
How full the server's disk is. Past 85% it shows in red: clear old backups below.
| KIND | HOW MANY | SIZE | CAN BE CLEARED |
|---|
Copies of every database kept in . One is made before every update (those go by themselves after 7 days). "Back up now" makes one more, which stays until you delete it. Delete moves a backup to the Bin on the Files page first. A backup older than 30 days that holds a client who was deleted is removed for good by itself (here and on the cloud drive), so that client's data is really gone; the newest backup always stays.
| NAME | KIND | MADE | SIZE | DATABASES |
|---|
Each update keeps the newest 3 versions of the app's programs. If an update goes wrong, switch the app's server program back to an earlier one. The database is not rolled back when you switch: it stays as it is now.
The version that was running before: .
A copy that leaves this server: straight to this computer's downloads, or straight to a cloud account you connect below. Nothing is left on the server afterwards. It is not locked with a passphrase: the passphrase would have to live on this same server, which protects nothing if the server is lost.
Off unless you tick it: then a cloud backup has every database but not the passwords. A backup downloaded to this computer always has the settings file. To stand the server back up from a cloud backup, the settings file is needed too: keep a copy somewhere safe.
Fixes for the server's own programs: Linux, PostgreSQL, TimescaleDB, Python, Caddy and the rest. Security fixes close holes that attackers already know about, so install them soon. If PostgreSQL or TimescaleDB is among the updates, a backup of every database is made first. Settings changed on this server are kept as they are.
| PROGRAM | NOW | NEW | KIND |
|---|
The server installs its updates by itself every night, so security fixes go in without anyone having to remember. A backup of every database is made first whenever PostgreSQL or TimescaleDB is among them. A bigger update (a new main version) is never installed by itself. Times are the server's own clock (UTC).
What runs on this server now. "Update now" and the nightly updates keep these up to date within their main version.
| PROGRAM | VERSION | NOTE |
|---|
Each database uses its own TimescaleDB version. After a TimescaleDB update, every database is brought up to the new one by itself.
| DATABASE | IN USE | NEWEST INSTALLED | STATE |
|---|
A browser that is not used for 12 hours is signed out. Changes that act on the whole server (on the Files tab, Updates, SSH keys, versions, backups that leave the server) ask for the 6-digit code again after 10 minutes.
Needs the password you use now and a 6-digit code. Every other browser signed in to this console is signed out; this one stays signed in.
For a new phone, or if someone else may have seen the setup key. Needs the password and a 6-digit code from the app you use now. A new code is shown once to scan; the old one keeps working until you type a code from the new one. Then every other browser is signed out.
Scan this with your authenticator app, then type the 6-digit code it shows for the new entry.
Cannot scan? Type this key into the app instead:
Signs out every browser signed in to this console, this one too. Use it if a computer or phone that was signed in is lost, or you are not sure who is signed in.