Connecting over SFTP

Using FileZilla, WinSCP or any SFTP client to move large amounts of data to and from your server.

Last updated: 2026-07-21

The browser file manager is fine for editing a config. For a modpack, a world you are migrating or a few hundred files, use SFTP — it is faster, resumes on failure and handles whole folders.

Your credentials

The SFTP connection tab shows everything you need:

Host — specific to the machine your server runs on, shown in the tab
Port — 2022, not the usual 22
Username — in the form srv. followed by your server's short ID
Password — the same password you use to sign in to the panel

The tab also has an Open SFTP link button that hands the connection straight to your default client, which saves typing all of it in.

The port catches people out. SFTP normally runs on 22; ours is on 2022. If your client says "connection refused", check that first.

Setting up a client

FileZilla — File → Site Manager → New Site, protocol SFTP, then fill in host, port 2022, username and password.

WinSCP — File protocol SFTP, same four fields.

Either way, the first connection asks you to trust the server's host key. That is normal for SFTP and only appears once per machine.

Passwords and subusers

There is no separate SFTP password. Your panel password is the SFTP password, so changing one changes both.

If you want to give someone file access without handing over your account, create a subuser and grant them file permissions. They connect with their own credentials and you can revoke them at any time.

Working safely

Stop the server before touching world data. The game keeps world files open while running and can overwrite whatever you upload the next time it saves. Configs are fine to edit live — they are only read at startup — but worlds are not.

Upload archives, extract on the server. Sending one 500 MB zip is far quicker than sending 4000 small files, and the file manager can extract it once it arrives.

Check the destination folder twice. Mods belong in /mods, plugins in /plugins. Files in the wrong folder are silently ignored — the server starts normally and simply behaves as if they were never there.

If the connection fails

"Connection refused" — almost always the port. It is 2022.

"Authentication failed" — the username has to include the srv. prefix exactly as shown in the panel. Copy it rather than typing it.

Connection drops on large transfers — lower the number of simultaneous connections in your client. FileZilla defaults to several at once; two is more reliable over SFTP.