Next steps

At this point, the SFTP server should be running — either via the installer or in portable mode. The installer creates an initial user during setup. If you skipped that step, add one now using the burusftp user add command.

Web Administration

If you installed the Web Administration component and it is running, you can manage the server through a web UI at http://localhost:8880 (default). Log in with the credentials you created during installation.

Web Administration is optional — the server can be fully configured through configuration files and the CLI.

If Web Administration is not running, you can set it up using burusftpwa svc install or start it manually with burusftpwa run.

Apply your license key

The trial version is fully functional for 30 days. To continue using the server after the trial period, apply a license key — either through Web Administration or by placing a license.key file in the configuration directory.

Add users

Add more users through the Web Administration panel or the burusftp user add command. For each user, you can configure virtual path permissions to control which directories are accessible and what operations are allowed, SSH shell access, authentication methods, and more.

To set up public key authentication instead of (or in addition to) passwords, see User Management.

Connect using SFTP

SFTP runs over SSH on port 22 by default. Common SFTP clients include WinSCP (Windows), FileZilla (cross-platform), and the OpenSSH sftp command (built into most operating systems).

Connection details:

Host: your server's IP address or hostname
Port: 22 (default)
Username and password: the credentials you configured

Connect using SSH

Beyond file transfers, Buru SFTP Server supports SSH shell sessions for remote command-line access and SCP file transfers. See Configure SSH Access for setup details.

Common SSH clients include PuTTY (Windows) and the OpenSSH ssh command (built into most operating systems).

Connection details are the same as for SFTP.

Connect using FTP/FTPS

FTP is disabled by default. Before connecting, you must enable FTP, configure endpoints, and set up TLS certificates. See Enable FTP/FTPS and Generate Self-signed X.509 Certificates (CLI).

Once configured, connect using an FTP client such as FileZilla (cross-platform) or WinSCP (Windows).