Transmission Bt

11/27/2021by admin
so every time i try to bring up the webui i get the following msg on my browser :Transmission

Transmission 3.00. Uses fewer resources than other clients. Native Mac, GTK+ and Qt GUI clients. Transmission is a lean, easy-to-use bittorrent client with support for encryption, a web interface, peer exchange, magnet links, DHT, µTP, UPnP and NAT-PMP port forwarding, webseed support, watch directories, tracker editing, global and per-torrent speed limits, and more.

403: Forbidden

In this Raspberry Pi Transmission tutorial, we will be showing you how to set up and configure the Transmission torrent client on your Raspberry Pi. Transmission is an excellent solution for torrenting on the Raspberry Pi. It is a relatively light client that is designed to use fewer resources than other torrent clients such as Deluge. Transmission-Qt is probably one of the fastest BitTorrent Clients.It sports a basic interface which takes advantage of all of the most recent torrent features. Unlike other BitTorrent clients like BitComet or uTorrent, Transmission-Qt is fast and completely unbloated.

Unauthorized IP Address.
Either disable the IP address whitelist or add your address to it.
If you're editing settings.json, see the 'rpc-whitelist' and 'rpc-whitelist-enabled' entries.
If you're still using ACLs, use a whitelist instead. See the transmission-daemon manpage for details.
I have tried to adjust the rpc settings and I cannot get anything to fix the problem. The only thing that works is for me to connect to my server and run this command : transmission-daemon -p 9091 -f -T -a
The last part is of course the exact ip of my laptop. How to I get access when my server runs the regular daemon at startup?


This document will show you how you can setup Transmission BitTorrent client on Alpine Linux and control it with a nice HTTP web-interface. I assume that you know the basics about Alpine Linux (package management and internals) and you have enough storage available to store your downloaded media (ie USB hard-drive) and of course a working internet connection.

Setting up Lighttpd with PHP support

The first thing we need to setup is lighttpd. We need lighttpd because our web-interface (Clutch) depends on PHP and the default webserver in Alpine Linux (mini_httpd) does not support it. Lets install it:

Transmission Bt

apk_add lighttpd php

NOTE: When you install PHP you will see it has some dependencies. PHP isn't a light package so please consider this before you install it.

When the installation is finished we need to add PHP support to lighttpd. There are two ways of adding PHP support to lighttpd:

  1. PHP in CGI mode
  2. PHP in FastCGI mode

If you need a high performance HTTP server with PHP support, you should probably go for the second option but if you need PHP only for some administrative tasks like controlling Clutch, CGI mode should be enough. FastCGI keeps PHP running in the background waiting for lighttpd to talk to it This makes it fast and more responsive than normal CGI mode. I choose normal CGI because I have a small embedded system and I prefer to use my memory for other things. Lets add PHP CGI support by creating the following file:

vi /etc/lighttpd/mod_cgi_php.conf

And add the following to it and save it:

Now we need to make sure lighttpd can find this configuration file by adding an include in our lighttpd.conf. You can add it inside the include section:

Our Lighttpd with PHP support should be complete. Lets start lighttpd and see if it works (make sure no other service is running on port 80).

/etc/init.d/lighttpd start

Fire up your prefered browser and point it to:

This should give a 404 document not found error. If not something went wrong... A good way of knowing if PHP is functioning properly is by creating a test page which includes the phpinfo() function. We do this like this:

echo '<? phpinfo(); ?>' > /var/www/localhost/htdocs/test.php

Now change the address in your browser to:

This should display a page which tells you everything regarding your PHP installation. If all is ok we can add lighttpd to the system start:

rc_add -k lighttpd

Setting up Transmission

As of Alpine 1.7.18 it includes Transmission BitTorrent client. Lets install it:

apk_add transmission

This should install Transmission 1.20 which is included in Alpine 1.7.18. After the installation is complete you should have default configuration file for init in:

We need to make some changes to this file. Because transmission-daemon will be controlled via Clutch which is run by lighttpd we need to change the user/group transmission-daemon runs at. We also need to change the DATA directory because we do not want to loose transmissions runtime info after a reboot (if it does it will need to recheck the hash of each running torrent). Personally I have mounted my USB disk to /media/usb and created a subdirectory torrents. This will be the directory where my media will be saved to. Inside this directory I created a .config directory. This is my DATA dir where transmission holds its runtime data. Make sure the torrents directory and everything below it is owned by lighttpd:lighttpd or else transmission cannot save any media. The contents of my conf.d file is like this:


If you need another DATA_DIR change it and save it. If you are sure that all permissions are setup correctly you can start transmission-daemon and see if all is working ok:

/etc/init.d/transmission-daemon start

If everything is OK you should see transmission-daemon running with the following command:


Lets add it to our system start:

rc_add -k transmission-daemon

Setting up Clutch WebUI

The last step is to install our web-interface. We do this by running:

apk_add clutch

After the installation completes it should be located in:

To make it available for lighttpd we need to make a symlink in the docroot of lighttpd:

ln -s /usr/share/webapps/clutch/0.4/htdocs /var/www/localhost/htdocs/clutch

Because we are adding a file outside /etc we need to add it with lbu add:

lbu add /var/www/localhost/htdocs/clutch

Clutch uses an configuration file which we can manage from the interface. The configuration file is stored outside our /etc directory so we will have to add it also with lbu add and we need to setup the proper permissions to the directory where its stored so clutch is able to write to it:

chown lighttpd:lighttpd /usr/share/webapps/clutch/0.4/htdocs/remote/data

lbu add /usr/share/webapps/clutch/0.4/htdocs/remote/data

Now it's time to see if our Clutch WebUI can find Transmission:

If everything is setup correctly it should return an error. This is because the default download directory is not setup correctly. In the left bottom corner of Clutch you will see a config button which will open the configuration window. Adjust your configuration and make sure you select a directory which is owned by the same user as transmission-daemon is running. After you save your settings you should have a working Clutch installation.

Saving your changes to disk

Transmission Bt Client

Now is a good time to write you changes to disk:

Transmission Bt Docker

lbu_commit device

Transmission Bt Blocklist

Retrieved from ''
Comments are closed.