How to connect to your server with SFTP
Upload and manage your server's files with an SFTP client like FileZilla, WinSCP or Cyberduck, using your team's SFTP password.
Updated · 2 min read
Every Schokr server supports SFTP, so you can manage its files with a desktop app instead of the web file manager. It’s the easiest way to upload large worlds, modpacks or whole projects, and to edit files in your own editor.
What you need
| Detail | Where to find it |
|---|---|
| Host and port | Your server’s SFTP connection details in the console |
| Username | Your server’s SFTP username, in the form name.serverid |
| Password | Your team’s global SFTP password, in team settings |
The SFTP password is shared across all of your team’s servers. The username is different for each server: the part after the dot identifies which server you’re connecting to.
Connect with FileZilla
- Install FileZilla (the client, not the server).
- Open File, then Site Manager, and create a new site.
- Set Protocol to SFTP - SSH File Transfer Protocol. Plain FTP won’t work.
- Enter the host and port from your server’s SFTP details.
- Set Logon Type to Normal, then enter your server’s SFTP username and your team’s SFTP password.
- Click Connect. You’ll see your server’s files on the right.
Connect with WinSCP or Cyberduck
The details are the same in any SFTP client:
- WinSCP (Windows): choose SFTP as the file protocol, then enter the host, port, username and password.
- Cyberduck (macOS and Windows): click Open Connection, choose SFTP (SSH File Transfer Protocol) and enter the same details.
Good habits
- Stop the server before replacing important files, like a world folder, so nothing writes to them mid-transfer.
- Upload code, not dependencies. Skip
node_modulesand Python virtual environments; let the server install them. - Keep the password private. Anyone with your team’s SFTP password and a server username can change that server’s files. If it leaks, change it in team settings.
- Watch your disk space. Everything you upload counts towards your server’s disk. See fixing a full disk.
Troubleshooting
- Authentication failed: check you’re using the SFTP username for that exact server (including the part after the dot) and the current team SFTP password.
- Connection refused or timed out: make sure the protocol is SFTP, not FTP or FTPS, and that you’ve used the port from your server’s SFTP details rather than 21 or 22.
- Permission denied on a file: your team role may not include file access. Ask a team owner, or see team roles and permissions.
Still stuck?
Ask on the Schokr Discord and include the client you’re using and the exact error.