Your server's IPv4 address is on its page under Instances, and in the provisioning email.
Log in
ssh root@203.0.113.10
The first connection asks you to accept the host key. Paste the root password from the provisioning email when prompted. On Windows, the same command works in PowerShell, Windows Terminal, or WSL.
Some images log in as a non-root user with sudo instead of as root. The
username for an image is login_username in
GET /api/v1/images, and it is shown on the server's page.
Change the password immediately
passwd
If SSH will not connect
Work through these in order.
Wrong address or not finished provisioning. Check the status on the server's
page. provisioning means there is nothing listening yet.
The cloud firewall is blocking it. If you set the inbound policy to DROP without an allow rule for TCP 22, SSH is gone. Fix it on the server's Network tab. See Cloud firewall.
Something inside the guest. A misconfigured sshd_config, a ufw
or firewalld rule, or a full disk. Use the browser console: it is a VNC
session straight to the guest and does not depend on SSH or on networking
working at all. See The browser console.
The account is suspended. A suspended server is powered off. Check Billing.
Locked out is recoverable
Between the browser console and a reinstall you can always get back in. Open a ticket if neither helps.
Next
Do not stop here. A brand new server with password SSH on port 22 is being brute-forced already: Harden a new server.