setup guides

the panel shows the ip as soon as the machine is provisioned. if you added an ssh key at order time, that is all you need:

ssh root@your.ip.address

no key? the panel showed a root password once, on the machine page. use it, then add a key and disable password login — a fresh ip gets its first brute-force attempt within hours of appearing on the network. that is not a scare story, it is what the auth log shows.

ssh-copy-id root@your.ip.address
ssh root@your.ip.address 'sed -i "s/^#*PasswordAuthentication.*/PasswordAuthentication no/" /etc/ssh/sshd_config && systemctl reload ssh'

generate a pair if you do not have one:

ssh-keygen -t ed25519 -C "looz"

paste the contents of ~/.ssh/id_ed25519.pub — the file ending in .pub — into ssh keys. the other file never leaves your computer and we never ask for it.

• add the domain in domains. we create the zone.
• at your registrar, replace the nameservers with the three shown on the zone page.
• back in the panel, press «направить» and pick the machine — it writes the A records for both the bare domain and www.
• give it up to 24 hours. nameserver changes are slow everywhere, not just here.

check what the world sees, not what the panel shows:

dig +short example.com @1.1.1.1

outgoing smtp is closed on new machines and opened on request after your first paid month. write to us with what the server sends and we usually open it the same day.

the reason is in the acceptable use policy: a brand-new server sending mail on day one is the most reliable signal of an abusive signup, and one of those blacklists the whole ip range — including your neighbour's.

there is no automatic backup. nothing is copied anywhere on a schedule, and we do not charge you for one — you take a snapshot yourself, from the machine page, and it takes about a minute.

• take one before anything risky: a rebuild, a resize, an upgrade you have not tried before.
• it lives with the same provider as the machine. that covers your own mistakes, not that provider disappearing.
• to roll back onto one, press «вернуться на этот снимок» next to it. the current disk is replaced by the state at the moment of the snapshot, and everything written since then is gone.
• keep your own copy of anything you cannot lose. this is not your archive.

• resize: the ip and the disk stay, so nothing on your side needs reconfiguring. the hours you already lived are billed at the old rate and the new one starts from the moment you switch — there is no prepayment to adjust. the new size applies on the next boot.
• rebuild: wipes the disk completely and reinstalls the image. snapshot first if you need anything off it.
• rescue: boots a temporary system with your disk attached — for when the machine will not come up on its own. enable it, then reboot.

this page covers the first week, not everything. ask at hello@looz.cloud and the answer becomes a section — that is how this list has grown so far.