Set Up Seafile as a Self-Hosted File Sync Server

Why Seafile Belongs on Your Home Server

Most cloud storage services give you convenience at the cost of control. Seafile flips that trade – it runs on your hardware, syncs your files at full local network speed, and keeps your data out of anyone else’s hands. Setting it up takes an afternoon, not a weekend.

What You Need Before You Start

Seafile runs on Linux, and the most straightforward path is a Debian or Ubuntu server – either a physical machine, a VPS, or a virtual machine on your home network. You will need root or sudo access, a working MySQL or MariaDB installation, and Python 3 available on the system. The server also requires at least 2GB of RAM to run comfortably under normal load, though 4GB is better if you plan to serve multiple users simultaneously.

Before downloading anything, set up your database. Log into MariaDB with mysql -u root -p, then create three databases: one for Seafile’s file data, one for the Seahub web interface, and one for the CCNET user management component. Name them something obvious – seafile_db, seahub_db, and ccnet_db work fine. Create a dedicated database user, grant it full privileges on all three databases, and flush privileges before exiting. Seafile’s installer expects these to exist before it runs, and it will fail ungracefully if they do not.

Next, download the latest Seafile server package from the official Seafile website. At the time of writing, the community edition is free and fully functional for personal and small-team use. Create a directory at /opt/seafile, move the downloaded tarball there, and extract it with tar -xzf. Inside you will find a versioned folder containing the setup script. Do not move files around manually – the installer is sensitive to its own directory structure.

Run the setup script with sudo ./setup-seafile-mysql.sh. The script walks you through a series of prompts: server name, server IP or domain, the path where uploaded files will be stored, and your database credentials. Enter the details methodically. For the file storage path, pick a location on a drive with enough space – /srv/seafile-data is a sensible choice. The script will create configuration files for all three Seafile components and confirm that each database connection succeeds.

Starting the Services and Configuring Seahub

Once setup completes, start the backend with ./seafile.sh start followed by ./seahub.sh start. The first time you launch Seahub, it will prompt you to create an admin account – enter an email address and a strong password. These credentials become your primary administrator login for the web interface. After that first run, subsequent starts require no additional input.

By default, Seahub listens on port 8000 and Seafile’s file transfer service listens on port 8082. If you have a firewall running – and you should – open both ports with ufw allow 8000/tcp and ufw allow 8082/tcp. Navigate to http://your-server-ip:8000 in a browser and log in with the admin credentials you just set. The interface is clean and functional: you can create user accounts, set storage quotas per user, and manage shared libraries from here.

For the server to be genuinely useful outside your local network, you need a reverse proxy sitting in front of it. Nginx works well for this – configure it to proxy requests from port 80 or 443 to port 8000 for the web interface, and separately proxy file transfer traffic on port 8082. If you already have a reverse proxy handling SSL termination on your server, routing Seafile through it follows the same pattern. The Seafile documentation includes ready-made Nginx configuration blocks that handle the Location /seafhttp block for file transfers correctly, which is easy to misconfigure manually. For a complete SSL setup with automatic certificate renewal, running Seafile behind Traefik as a reverse proxy handles the certificate management side without additional configuration.

Edit ccnet.conf to update the SERVICE_URL to reflect your domain name or public IP address – for example, https://files.yourdomain.com. In seahub_settings.py, set FILE_SERVER_ROOT to your domain followed by /seafhttp. These two settings tell the desktop and mobile clients where to send file transfers, and getting them wrong is the most common reason sync appears to work but file uploads quietly fail. After changing either file, restart both services for the changes to take effect.

To make Seafile start automatically on boot, create systemd service files for both components. Each unit file should call the respective shell script with the start argument and set the working directory to your Seafile installation folder. Enable them with systemctl enable seafile seahub, and from that point forward the server comes back up after a reboot without any manual intervention.

Installing the Client and Syncing Your First Library

Seafile’s desktop client is available for Windows, macOS, and Linux. Download it from the Seafile website, install it, and point it at your server address during setup. After logging in, you can create libraries – Seafile’s term for synced folders – and choose which ones to sync to each machine. Libraries are encrypted individually, and you can set a password on any library so that even the server administrator cannot read its contents without the key. That per-library encryption is something most self-hosted sync tools do not offer at the folder level.

The mobile apps on Android and iOS follow the same pattern: server address, credentials, and then a file browser that lets you star files for offline access or upload directly from the camera roll. One practical consideration worth flagging – if your server certificate is self-signed rather than issued by a public certificate authority, the mobile apps will refuse to connect unless you explicitly allow untrusted certificates in the app settings. Using a real domain with a Let’s Encrypt certificate sidesteps this entirely and is worth the extra setup time if mobile access matters to you.