Quick start
From nothing to a Postgres you can open. This path uses Tailscale. Headscale and OpenVPN are the other two. A second copy of a database, for reads and for failover, is replication.
If you are not satisfied with the service, the most recent month is refunded. Forward that to your appointed technical support representative. We will respond within 1 hour. Canceling early does not prorate the month that is running. The terms say the rest.
1. A Tailscale account
Skip this if you already have a tailnet. Otherwise create a Tailscale account. The free personal plan is enough for one database.
2. Install Tailscale
Install Tailscale on the computer you will connect from, and sign that computer into the tailnet. Leave it running. The database is not on the public internet. Your machine reaches it through Tailscale.
Turn on MagicDNS so the database has a name, not only an address. HTTPS certificates are optional. When they are on, Tailscale can issue the certificate. When they are off, Nandling signs one for that database.
3. A Nandling account
Create the account. An account can include 10MB of reserve. The password is at least 10 characters.
4. Request 10MB of reserve
On Databases, under 10MB reserve, choose Request 10MB of reserve. That adds 10MB to the account pool. It does not create a database. If a grant is open, it is added. You assign it when you create or resize a database.
If none is open, the request still goes in. It can take a while. The page says so. You do not need to request it again.
5. An auth key
In Tailscale, open Settings, then Keys, and generate an auth key. Tailscale’s auth key guide covers the same screen.
- Reusable, so another database on this account can join later.
- Tagged
tag:nandling. - Not ephemeral. An ephemeral node disappears when it stops, and the address goes with it.
- Pre-approved, so the database can come back on its own.
The ACL that lets your devices open port 5432, and does not let the database wander the rest of the tailnet, is on the connect page. Tailscale’s ACL reference is the long version. A broader allow-all rule you already have still applies.
6. Paste the key
On Databases, Network stays on Tailscale. Paste the key into Auth key and save. Leave the field blank later if you are not replacing it. One key enrolls every database on the account.
A single database can have its own key. Open that database, Network, paste it there, and save. A key saved on the database is the one that database uses.
The database joins on its own. The page shows a network name when it is up. That can take a minute after the key is saved.
7. The Postgres client
Install the PostgreSQL client. You want psql. Postgres is already running. You only install the client.
Open the database in Nandling. The page has the user, the password, and a connection line. It looks like this, with the name from that page:
psql "host=NAME port=5432 user=USER dbname=USER sslmode=require"
require encrypts and does not check the name. verify-full also checks the name. The connection is TLS only. Moving data is pg_dump into and out of this database.
8. Stop and start
Stop is for a connection that is stuck. The data stays. Start brings Postgres back. A snapshot of this database is on the database page. It is included, and it is not a file you can download.
9. Snapshots
A snapshot is a copy of one database, taken while it is running. Five snapshots you ask for are kept for each database. A nightly one is optional, and seven of those are kept. Neither one changes the price. The megabytes you already pay for are the whole charge.
Snapshots are stored on a backup server next to the production database network. They are not on the public internet. Each one is encrypted before it is stored. Nandling keeps a keychain: it makes a key, rotates that key, and keeps every previous key, because an older snapshot still opens with the key that wrapped it. A second key, kept offline, can also open every snapshot. If the keys on the service were lost, that offline key can still open the file. Nandling can decrypt a snapshot in order to load it back. That is what a restore is.
On the database page, Snapshots lists the ones for that database. Take a snapshot asks for one. It shows up in the list when it is stored. Load into this database replaces what is in a database on this same account. New database from this snapshot opens another database, under the same rules as any new database, and fills it from the snapshot. Removing one takes it off the account and deletes the encrypted file.
A snapshot cannot be downloaded, and a file cannot be uploaded to become one. Moving data in and out by hand is still pg_dump of that one database. A snapshot is only restored into a database on the account that owns it.
Closing the account deletes its snapshots along with the databases. Nightly snapshots stop when you turn them off, and the ones already stored stay until they age out or you remove them.
A replica is a second copy on another server. It reserves the same size again, it is read over your tailnet, and writes can move to it. Replication, the second key, and failover.
Extensions lists the ones this Postgres has, and the ones it does not.