The main steps in understanding about a seedbox are
1.Renting a Seedbox
2. Setup a Seedbox
3. How to administer a seedbox
4. Use it for torrents and buld up ratio
Linux is the preferred oS or seedboxes because it is less resource hungry than other OS available.
Seedbox Definition: Dedicated computer used to seed torrents, mostly it is done on rented servers which have high bandwidth ranging from 10MBPS to 10 GBPS.
1. No ISP limitations
2. Insane speeds for seeding
3. Seeding occurs 24X7
4 . Lot of people in private trackers use Seedboxes hence a lot of the seeders prefer from own network , which definitely boosts your ratio.
5. None of the resources of your home Personal computer is used.
Steps to get your Seedbox.
Find a seedbox company with decent space and bandwidth 100mbps is good for most of the cases also transfer cap is huge , you can get a decent working seedbox for anywhere around 14-20$, if you are a beginner I would suggest try for CUtorrents , their basic plan is 14$ , 500 GB space , 100 MBPS unmetered , private trackers only – I would suggest you to keep away from public trackers as they will drain always lot of resources from your seedbox and its is better to stay away from them because they could be monitored. Said that this is the seedbox I am using right now the speeds are good and only 6 people per server ut is one of the cheapest and best seedboxes out there.
Hosting your own seedbox
If youw sih to you can host your own seedbox the tutorials are available on the website , Centos OS is a free OS that is available on which you can easily install your seedbox the tutorial you can find here LINK
Dedicated server = You get a single server all to you.With all the resourses.
VPS: Virtual Private Server: Its one dedicated server distributed into several virtual dedicated servers , it is private server so whatever minimum specification you but stay with you at any cost , it is as good as any dedicated server and the best part is it is much more cheaper than a dedicated server.
You can get your VPS or dedicated hosting from Rosehosting , you can customise your own VPS I think that option is great and the prices are also low as compared to others.The best part is the unmetered data transfer which you will hardly find in any VPS providers, what you could do with a unmetered VPS — Well I would like to leave that to your imagination.
2. Getting started
Let’s start at the most basic of basics: Connecting to your server. Once it has been set up you’ll receive an IP or hostname to connect to along with root account information (with either a generated password or one you chose.) Connecting is done via SSH and is usually left on the default port of 22. To connect you’ll need a client. On Windows, the best client available is PuTTY which is open source. On Macs you can use the ssh command from a terminal.
# PuTTY tutorial: http://www.cs.rit.edu/~atg2335/putty/
Once logged in you’ll be faced with a prompt similar to Fig.1. This is known as the bash shell and is the default for most current Linux distros.
Fig.1 SSH login prompt
What are some standard Linux commands?
# cd : Change directory
# ls : List directory contents
# rm : Remove file (or directory with -r option)
# mv : Move file
# cp : Copy file
# cat : Echo file contents to stdout
# pwd : Print working directory
# grep : Search input for string
# ps : List processes
# su : Substitute user
# exit : Terminate SSH session
# man : Lookup manual pages for command
If you’re unfamiliar with Linux I would recommend reading some of the many Linux introductions available. A quick search on Google will net you many helpful pages with more than enough information to get you started. You should understand what it is you’re doing rather than blindly following along. When in doubt about how to use a command, check its man page. They are filled with useful information about what the command does, and how to use it.
IMPORTANT: Familiarize yourself with the vi text editor! Take the time to go through a tutorial. You should at least know how to switch modes (i for edit, esc for command), save files (:w), search (/ and ?) and quit (:q).
What exactly will we be using for this seedbox?
# lighttpd with php-fastcgi
# vnstat w/ PHP frontend
vnstat will be used to monitor bandwidth usage with a PHP frontend served with lighttpd. Having lighttpd set up will also make future addition of a webui for rTorrent relatively painless (once a decent one is available.) Before we dive into setting all of this up though, it’s important to secure your server.
With any luck your fresh-out-of-the-oven server will be attacked within the first few hours of it coming online. Security is extremely important. Always keep security in mind! The last thing you want is for someone to put a rootkit on your server and start eating up your bandwidth DDoSing, or getting you into trouble for what they do with it.
# Update your packages
Your packages (installed software) may be out of date so it’s a smart idea to get everything updated just in case any security flaws have been patched
# yum update
Loading “installonlyn” plugin
Setting up Update Process
Total download size: 19 M
Is this ok [y/N]: y
# Configure a new user
It is important to set up a non-root user for yourself. It should go without saying, but use a password that is difficult to guess (mixed case, numbers, longer than 8 characters.) I also recommend using a username that is difficult to guess, as without a valid username, there is no password to bruteforce.
# useradd username
# passwd username
Changing password for user username.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
If you plan on having other user accounts you may want to only allow users in the wheel group to su. This step can differ between distros. Using vi, edit /etc/pam.d/su and remove the # before the following auth line:
# Uncomment the following line to require a user to be in the “wheel” group.
auth required pam_wheel.so use_uid
Press i to edit, then ESC to get back to command mode. Type :wq to save and quit. After saving, add your new user to the wheel group and verify its group memberships:
# usermod -a -G wheel username
# groups username
username : username wheel
# Reconfigure OpenSSH
Open /etc/ssh/sshd_config with vi and find the line with Port (enter /Port in command mode to search.) Change it to a number above 1024, I personally go with a 5-digit number no greater than 30000. Make sure you update your profile in your client to use the new port in future connections. While in sshd_config you should make some other changes, so edit or verify that the following settings match these values:
Fig.2 Example banner
Save and exit, and if you chose to use the Banner option in sshd_config, create the file with vi. Fig.2 shows a banner example. Once you have made the needed changes, you’ll need to restart the ssh daemon. Do so with the following command
# service sshd restart
# Fig.3 Restarting SSHd
If there were errors SSH will fail to restart. Go back over your config and make sure you haven’t made any errors in the syntax. Fix any problems and try again. If SSHd restarted, it’s time to test your non-root login. Open a new instance of your client (don’t disconnect your first one yet!), connect to your server on the new port and login with the user you made previously. If you try to login to your root account you will not be able to because of the new SSHd settings. Try executing the su – command to get a root prompt
$ su –
If you have problems connecting to the new port, chances are there are firewall rules in place and you’ll have to explicitly open the new port. In my case the following would be sufficient:
# iptables –list
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all — anywhere anywhere
# iptables -I RH-Firewall-1-INPUT 3 -p tcp -m tcp –dport 19191 –tcp-flags SYN,RST,ACK SYN -j ACCEPT
# iptables-save > /etc/sysconfig/iptables
The argument -dport 19191 is the opened port. If you have trouble opening ports try asking your host for information on how to do so.
Many other security measures can be put in place, but those techniques are beyond the scope of this basic guide. As always, Google is your friend for this subject.
Some topics worth reading up on:
SSH authentication via Private/Public key pairs
If you do not need a webserver you can skip ahead to installing vnstat
# Install and configure lighttpd + PHP
lighttpd is a lightweight, efficient http daemon which we will use for our webserver along with PHP. We must first add the DAG repository:
Then it’s as simple as following these commands:
# yum install lighttpd lighttpd-fastcgi php-cli php-gd php-mysql
Total download size: X M
Is this ok [y/N]: y
# chkconfig –levels 235 lighttpd on
chkconfig is used to configure the run levels of the lighttpd service. In the event of a reboot, lighttpd will now start properly on its own.
From here we must configure PHP and lighttpd to our liking. We need to make a small change to php.ini, so issue the following command:
# echo ‘cgi.fix_pathinfo = 1’ >> /etc/php.ini
Make sure you use >> and not > or you will erase the entire file. In /etc/lighttpd/lighttpd.info some more detailed changes must be made. Open the file in vi and find the server.modules section, and uncomment mod_fastcgi and mod_simple_vhost.:
server.modules = (
Uncomment and configure the following settings under virtual hosts
simple-vhost.server-root = “/srv/www/vhosts/”
simple-vhost.default-host = “mydomain.com”
simple-vhost.document-root = “/htdocs/”
Also find and configure
server.document-root = “/srv/www/vhosts/”
simple-vhost is a way to host multiple domains on the same server and works quite well for our purposes. A path to say, tflux.mydomain.com would end up being /srv/www/vhosts/tflux.mydomain.com/htdocs/
Further down in lighttpd.conf you’ll find the following block, which you’ll need to uncomment and edit like so:
#### fastcgi module
## read fastcgi.txt for more info
## for PHP don’t forget to set cgi.fix_pathinfo = 1 in the php.ini
fastcgi.server = ( “.php” =>
( “localhost” =>
“socket” => “/tmp/php-fastcgi.socket”,
“bin-path” => “/usr/bin/php-cgi”,
“max-procs” => 1,
“bin-environment” => (
“PHP_FCGI_CHILDREN” => “1”
max-procs and PHP_FCGI_CHILDREN are used to limit the memory usage lighttpd can take up with PHP children. These lines are optional but recommended to conserve memory.
Save the config and issue the following commands to create your new directory tree for lighttpd
# mkdir -p /srv/www/vhosts/mydomain.com/htdocs
# chown -R lighttpd:lighttpd /srv/www/vhosts
# chmod -R 775 /srv/www/vhosts/*
You should now be all set to start lighttpd.
# /etc/init.d/lighttpd start
If there were errors, go over your configs and make sure that everything was properly configured.
# Install vnstat & frontend
vnstat is painless to set up and is extremely useful in monitoring your bandwidth usage. It’s important to figure out what the logical name for your NIC is, so let’s identify it using ifconfig.
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:9487236 errors:0 dropped:0 overruns:0 frame:0
TX packets:8652113 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:4251125510 (3.3 GiB) TX bytes:4014294429 (3.1 GiB)
That, for example, is my server NIC. It is far more common for it to be named eth0, but I included mine to show that it can differ. This name is needed for the next step, installing and configuring vnstat. The final command is used to tell vnstat to create a database for the venet0 interface, which we’ll be configuring the webui to use.
# yum install vnstat
Total download size: X M
Is this ok [y/N]: y
# vnstat -u -i venet0
If you did not install a webserver you can skip installing the frontend
Next is the web frontend for vnstat.
# mkdir -p /srv/www/vhosts/vnstat.mydomain.com/htdocs
# wget http://www.sqweek.com/sqweek/files/v…end-1.3.tar.gz
# mkdir /srv/www/vhosts/mydomain.com/htdocs/vnstat
# tar -zxf vnstat_php_frontend-1.3.tar.gz -C /srv/www/vhosts/mydomain.com/htdocs/vnstat/
# chown -R lighttpd:lighttpd /srv/www/vhosts/*
Before you can use the frontend properly you must also edit config.php in your new vnstat directory using the name of the interface you found in the previous step
$iface_list = array(‘venet0’);