SFTP Access

The browser file manager (see Managing Files) is fine for quick edits, but for large uploads — a full world, a modpack, hundreds of plugin files — a dedicated SFTP client (FileZilla, WinSCP, Cyberduck, or your code editor’s built-in SFTP support) is faster and handles interrupted transfers better. For a step-by-step walkthrough of the two most common clients, see Connecting with an SFTP Client.

Finding Your Details

Go to the Settings tab — the SFTP Details card shows everything you need:

Server Address — sftp://<node-hostname>.atomichost.co.za:<port>. This is a different hostname than the one players connect to (see Connecting to Your Server) — it points at the physical machine (node) your server runs on, not the game’s own network allocation.
Username — in the form <your-account-name>.<short-server-id>, unique per server.

Note

Your SFTP password is the same password you use to log into the panel itself — there’s no separate SFTP password to look up or reset.

Click Launch SFTP to hand the address straight to your system’s registered sftp:// handler, if you have one configured.

Connecting Manually

If your client asks for the pieces separately rather than taking a single sftp:// link:

Field	Value
Host	The hostname from Server Address, without `sftp://`
Port	The number after the `:` in Server Address
Username	From the SFTP Details card
Password	Your panel account password
Protocol	SFTP (not FTP, and not FTPS)

What You Can Do Over SFTP That You Can’t in the Browser

It’s the same filesystem either way, but there’s one hard limit: the browser file manager caps uploads at 100MB per file. Anything bigger — most worlds, most modpacks — has to go over SFTP, which has no such cap. Beyond that, the rest is convenience at scale: resuming a large interrupted upload, syncing a local folder with a proper sync tool, or editing files with your own local editor instead of the in-browser one.