Install cross-seed
This guide explains how to install cross-seed in your home directory without root access.
Requirements
- Node.js is required before installing cross-seed.
- cross-seed requires Node.js 20 or newer.
- If you do not have Node.js installed yet, please follow this guide first: Node.js Installation.
1. Log in to your account via SSH and verify your Node.js installation:
node -v npm -v
If both commands return a version number and your Node.js version is 20 or newer, you can continue.
2. Install cross-seed:
npm install -g cross-seed
3. Verify the installation:
cross-seed --version
cross-seed has been installed successfully.
Create a Configuration File
Generate the default configuration file:
cross-seed gen-config
The configuration file will be created in:
~/.cross-seed/config.js
Edit the configuration using your preferred text editor, for example:
nano ~/.cross-seed/config.js
Run cross-seed
To start cross-seed, simply run:
cross-seed
Run cross-seed in the Background
To keep cross-seed running after you disconnect from SSH, start it inside a detached screen session:
Start cross-seed:
screen -DmS cross-seed cross-seed
Verify that it is running:
screen -ls
Attach to the running session:
screen -r cross-seed
Stop cross-seed:
screen -S cross-seed -X quit
Update cross-seed
To update cross-seed to the latest available version, run:
npm install -g cross-seed@latest
Then verify the installed version:
cross-seed --version
cross-seed has been updated successfully.
Uninstall cross-seed
To remove cross-seed from your account, run:
npm uninstall -g cross-seed
If you also want to remove the configuration files, run:
rm -rf ~/.cross-seed
cross-seed has been removed successfully.
Notes
- Node.js 20 or newer is required.
- cross-seed is installed entirely inside your home directory and does not require root access.
- You need to configure your torrent client and indexers in
~/.cross-seed/config.jsbefore using cross-seed. - Supported torrent clients include rTorrent, qBittorrent, Deluge and Transmission.
- If the
cross-seedcommand is not found after installation, log out of your SSH session and log back in.