![]() If you are running iptables, firewalld, or ufw, be sure to open port 80 and port 443 if you are using SSL on the server where Apache is running. In either case, restart the httpd service: service httpd restart SSLCertificateKeyFile "/etc/pki/tls/private/server.key" Then, create /etc/httpd/conf.d/nf with the following contents: NameVirtualHost *:80ĮrrorLog logs/-ssl_error_logĬustomLog logs/-ssl_access_log common #TRANSMISSION TORRENT PROXY SETTINGS INSTALL#If you do care about encrypting the traffic between you and the Transmission web interface, install the mod_ssl package: yum install -y mod_ssl If you don’t care about encrypting the traffic between you and the Transmission web interface, create /etc/httpd/conf.d/nf with the following contents: NameVirtualHost *:80ĮrrorLog logs/-error_logĬustomLog logs/-access_log common Remember to change and in the examples below to match whatever domain names you are using. ![]() Install the Apache web server: yum install -y httpd The following steps are specific to Fedora and Enterprise Linux based distributions, but they can be easily adapted to work on other Linux distributions.įirst and foremost, if you are using SELinux, and you should be, be sure to turn on the following SELinux boolean, otherwise nothing will work: setsebool httpd_can_network_connect on Make sure your VPN client has kill switch and DNS leak options enabled. This is even more useful if you have the transmission-daemon service setup for authentication usernames and passwords should never be sent in plain text. There arent any particular torrent client settings you need, its mostly the VPN client you need to configure. Second, with the transmission-daemon service behind Apache, you can easily setup SSL to encrypt all of the traffic between you and the Transmission web interface (this is not encrypting actual bittorrent traffic). However, if the transmission-daemon service and the Apache service are running on the same server you can continue to use. Why did I use instead of ? If the transmission-daemon service and the Apache service are running on different servers you will have to use different hostnames. ![]() Why would you want to put the transmission-daemon service behind an Apache Reverse Proxy?įirst, it will allow you to navigate to a simpler URL such as instead of. Port 80 is a restricted port and requires the service to be running as root or to have the appropriate CAP_NET_BIND_SERVICE capability.Ī second option is to put the transmission-daemon service behind an Apache Reverse Proxy. By default, making this change will not work. To accomplish this, one option would be to change the rpc-port parameter in /var/lib/transmission/.config/transmission/settings.json to port 80 instead of port 9091. While remembering to append port 9091 is not difficult, it would be much cleaner to just go to. Assuming the service is running and the proper firewall holes have been made, the Transmission web interface can be accessed by going to. By default, the transmission-daemon service uses its own web server and runs on port 9091.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |