Set Up Seafile as a Self-Hosted Dropbox Alternative

Why Self-Hosted Cloud Storage Makes Sense

Dropbox, Google Drive, and iCloud are convenient until you start thinking about what happens to your files once they leave your device. Your documents, photos, and project files sit on servers you do not control, subject to pricing changes, storage caps, and terms of service that can shift without much warning. Seafile offers a way out – a self-hosted file sync and sharing platform that works like Dropbox but runs entirely on your own hardware, whether that is a home server, a VPS, or a spare machine tucked under a desk.

The setup takes a little more effort than downloading an app, but the payoff is complete ownership of your data with no monthly fees, no storage limits beyond your own disk space, and no third-party access. Seafile supports desktop sync clients, mobile apps, file versioning, encrypted libraries, and team sharing – meaning you give up almost nothing compared to mainstream cloud storage.

What You Need Before You Start

Seafile runs well on modest hardware. A machine with 2GB of RAM and a dual-core processor handles a personal or small-team install without breaking a sweat. You will need a Linux server – this guide uses Ubuntu 22.04 LTS, which is the most common and well-supported target for Seafile. You also need a domain name or static local IP address so that sync clients can find your server reliably, and either MySQL or MariaDB to store Seafile’s metadata.

Before installing anything, make sure your server is up to date. Run sudo apt update && sudo apt upgrade -y and reboot if the kernel is updated. You should also have a non-root user with sudo access set up and a basic firewall configured. Open port 80 and 443 if you plan to run Seafile behind a reverse proxy with HTTPS, which is strongly recommended for any install that will be accessible outside your local network.

Installing Seafile on Ubuntu

Start by installing the required dependencies. Seafile needs Python 3, pip, and several Python libraries alongside MariaDB. Install them with: sudo apt install -y python3 python3-pip python3-setuptools python3-mysqldb mariadb-server nginx. Once that finishes, secure your MariaDB install by running sudo mysql_secure_installation and following the prompts to set a root password and remove anonymous users.

Next, create two databases – one for Seafile’s file metadata and one for its web interface, Seahub. Log into MariaDB with sudo mysql -u root -p, then run the following commands, replacing yourpassword with something strong:

• CREATE DATABASE ccnet_db CHARACTER SET utf8;
• CREATE DATABASE seafile_db CHARACTER SET utf8;
• CREATE DATABASE seahub_db CHARACTER SET utf8;
• GRANT ALL PRIVILEGES ON ccnet_db.* TO ‘seafile’@’localhost’ IDENTIFIED BY ‘yourpassword’;
• GRANT ALL PRIVILEGES ON seafile_db.* TO ‘seafile’@’localhost’;
• GRANT ALL PRIVILEGES ON seahub_db.* TO ‘seafile’@’localhost’;
• FLUSH PRIVILEGES;

Now download the latest Seafile server package from the official Seafile website. At the time of writing, the community edition is available as a tar.gz archive. Create a dedicated directory with mkdir -p /opt/seafile, move the archive there, and extract it with tar -xzf seafile-server_*.tar.gz. Change into the extracted directory and run sudo bash setup-seafile-mysql.sh. The setup script walks you through naming your installation, setting your server’s IP or domain, and connecting to the three databases you just created.

Once the script completes, start the services with ./seafile.sh start followed by ./seahub.sh start. The first time you start Seahub, it asks you to create an admin email and password – this becomes your login for the web interface. If everything runs without errors, Seahub is accessible at http://your-server-ip:8000. Log in with your admin credentials and you will see the Seafile dashboard.

Setting Up HTTPS with Nginx

Running Seafile over plain HTTP is fine for testing on a local network, but any setup you want to use day-to-day should sit behind HTTPS. Nginx works well as a reverse proxy here. Create a new Nginx config file at /etc/nginx/sites-available/seafile with a server block that proxies requests on port 443 to Seafile’s internal ports – 8000 for Seahub and 8082 for the file transfer service. Point your SSL certificate paths at certs issued by Let’s Encrypt using Certbot.

Install Certbot with sudo apt install certbot python3-certbot-nginx -y, then run sudo certbot –nginx -d yourdomain.com. Certbot edits your Nginx config to add the SSL directives and sets up automatic renewal. After that, update Seafile’s own config files – specifically ccnet.conf and seahub_settings.py – to reflect your HTTPS domain rather than the bare IP. Restart both Nginx and Seafile services, and your instance is now running over an encrypted connection.

Connecting Clients and Enabling File Sync

Seafile provides desktop clients for Windows, macOS, and Linux, all available from the official Seafile website. After installing the client, point it at your server’s URL and log in with your admin credentials or a separate user account you have created through Seahub. The client creates a local Seafile folder on your machine and keeps it in sync with the server – exactly the same experience as Dropbox, just talking to your own hardware.

On mobile, the Seafile app is available on both Android and iOS through their respective app stores. The mobile client lets you browse libraries, upload photos, and mark files for offline access. For teams or household members sharing the same server, you can create additional accounts through the Seahub admin panel at http://yourdomain.com/sys/useradmin/ and assign each user a storage quota to keep disk usage predictable.

Seafile also supports encrypted libraries – a feature that sets it apart from most basic self-hosted alternatives. When you create an encrypted library, files are encrypted on the client side before being uploaded to the server. Even if someone gains access to your server’s storage directory, the files are unreadable without the library password. This is worth enabling for anything sensitive, and it requires no extra configuration beyond choosing the encrypted option when creating a new library in Seahub or the desktop client. If you are already running other backup infrastructure, pairing Seafile with an offsite backup solution like Restic for automated encrypted backups gives you a second layer of protection for the data Seafile manages.

Keeping Seafile Running Long-Term

Seafile does not manage itself after install, so setting up systemd service files is worth the ten minutes it takes. Create service files for both seafile.service and seahub.service in /etc/systemd/system/. Each file should point to the relevant start script in your Seafile install directory and set Restart=on-failure so the services come back automatically after a crash or reboot. Run sudo systemctl enable seafile seahub to make both services start at boot.

For updates, Seafile releases new versions regularly. The upgrade process involves downloading the new package, stopping both services, running the provided upgrade script inside the new version’s directory – for example ./upgrade/upgrade_10.0_11.0.sh – and then restarting. Always back up your databases and the /opt/seafile/seafile-data directory before upgrading. The upgrade scripts handle database schema migrations, but having a known-good backup removes any risk from the process.

One thing to keep in mind as your Seafile library grows: Seafile stores files as chunked blocks on disk rather than as recognizable files in a folder structure. This means you cannot just browse to the storage directory and find your files – you need Seafile running to access them. If you ever need to migrate to a new server, the process is straightforward as long as you move both the databases and the seafile-data directory together, but it is a detail worth understanding before you start storing terabytes of irreplaceable files and expecting a simple drag-and-drop recovery.