Connecting to Your Server with SFTP (Port 8822)

SFTP on LOW.MS runs on port 8822, and you log in with the same username and password you use for the control panel. Any SFTP app works. I'll use FileZilla here because it's free and it's what most of our tickets mention.

File Manager is fine for a config edit or two. Once you're moving a whole world, a modpack or a few hundred files, SFTP is quicker and far less likely to time out halfway through.

Your SFTP login details

You need four things:

• Host: your server's IP address. It's the part before the colon in the address shown on your service page in the control panel, so 203.0.113.25:7777 means a host of 203.0.113.25.
• Port: 8822. Not 22, not 21, and not your game port.
• Username: your control panel username. Not your email address.
• Password: your control panel password.

That's one login for every server on your account. Sub-users you've made log in with their own username and password.

Don't know your control panel password because you always come in through the billing area? Open a ticket and we'll sort it, since the SFTP password is the same one.

Connecting with FileZilla or WinSCP

Grab FileZilla Client from filezilla-project.org (not FileZilla Server, people download the wrong one all the time). Then:

1. Open File, then Site Manager, and press New site.
2. Set Protocol to SFTP - SSH File Transfer Protocol.
3. Put your IP in Host and 8822 in Port.
4. Set Logon Type to Normal and fill in User and Password.
5. Press Connect.

The first connection pops up an Unknown host key warning. That's expected. Tick Always trust this host, add this key to the cache and press OK.

You can use the Quickconnect bar instead, but type sftp:// in front of the IP. Leave it off and FileZilla tries plain FTP, which fails on 8822.

WinSCP is the same idea: pick SFTP as the file protocol and use the same four details.

Tip: plain FTP also works, on port 8821 with the same login. SFTP is encrypted though, so use it unless your app can't.

Where your files are

Once you're in, you'll see a folder for each of your servers, named after its IP and port, something like 203.0.113.25_7777. Everything for that server lives inside it, laid out the same way File Manager shows it.

Every game puts its saves and configs somewhere different. Our save location guides cover where the world sits for each game, for example Palworld, 7 Days to Die and Valheim.

Stop the server before you replace a save. A running server keeps writing to its world, and it'll happily overwrite what you just uploaded. On some games the files are locked while it runs anyway, so the upload just fails.

Gotcha: some config files are rewritten by the control panel every time the server starts. If a setting has a box in Service Settings or a file in Configuration Files, change it there, otherwise your edit gets put back on the next restart.

Files you can't upload

SFTP has the same upload filter as File Manager. Programs and scripts are blocked: .exe, .dll, .so, .bat, .sh, .cmd, .vbs and a few other executable types. FileZilla shows a permission error and moves on, so check the Failed transfers tab at the bottom after a big upload.

This catches people out with mods. Everything in a mod folder uploads except the .dll, so the folder looks installed and nothing happens in game. BepInEx mods on Valheim and Core Keeper are the usual culprits, along with native UE4/UE5 mods.

What to do instead:

1. Check Mod Manager in the control panel first. A lot of popular mods and frameworks are there as one-click installs, and the panel puts the DLLs in for you.
2. If your mod isn't there, open a ticket with a link to it and we'll install it.

Text files, configs, saves, maps, .pak files, .lua scripts and .zip archives all upload normally.

When it won't connect

"Cannot establish FTP connection to an SFTP server". That's FileZilla talking FTP to an SFTP port. Set the protocol to SFTP, or add sftp:// in front of the IP.

Timed out or connection refused. Nine times out of ten it's the port. Check it's 8822.

"Authentication failed". Make sure the username is your control panel username, not your email. Then try the same password on the control panel. If that fails too, it's the password.

Uploads fail partway through a folder. Look at Failed transfers. If it's only .dll or .exe files, see the section above. If it's save or config files, stop the server and try again.

Still stuck? Open a ticket and paste the last few lines of FileZilla's message log. It usually tells us exactly what went wrong.