Home
ruTorrent is a web frontend for rtorrent designed to emulate the look and feel of µTorrent WebUI so its appearance is quite similar to the "parent". The name "ruTorrent" is the combination of µTorrent and rtorrent.
The original version of ruTorrent was based on an older version of µTorrent Webui but has been completely rewritten as of 3.0.
- rtorrent 0.8.2 or later, compiled with xmlrpc-c support. If you don't know where to get it for your system, you are suggested to visit rtorrent official site.
- Web-server with PHP 7.4
- PHP Extensions: php-mbstring, php-dom, php-libxml (including but not limited to)
- Browser as a local client:
- Firefox 2.x - 31.x - for optimal compatibility.
- All versions of Internet Explorer - not supported.
- Konqueror 3.5.9 - OK, except charts on tabs Speed and Traffic.
- Opera 9.x/10.x - works fine.
- Safari 3.x - works, but pictures may not be displayed when https-protocol is used. Probably this is a browser issue. Try to adjust a server not to make keep-alive connections.
- Google Chrome 4.1.249.1045 - the same as Safari.
- rtorrent 0.9.8, compiled with xmlrpc-c support. If you don't know where to get it for your system, you are suggested to visit rtorrent official site.
- Web-server with PHP 8.1 or 8.2
- PHP Extensions: php-mbstring, php-dom, php-libxml (including but not limited to)
- Browser as a local client
- Latest version of Firefox, Google Chrome, Safari, Opera, Microsoft Edge etc.
For detailed setup and configuration information, see rtorrent installation, Web Server Setup and ruTorrent config. If you have an issue, a bug or a question, open a ticket.
- Authentication - Currently ruTorrent does not have any sort of authentication. For authentication, use whatever your webserver supports.
- Only enable the "Receive messages from tracker" option in the Settings panel for rtorrent version 0.8.5 or later. Otherwise it can lead to a crash because of incorrect processing of tracker's messages, containing non-UTF-8 characters, by rtorrent.
- rtorrent Settings, changed by the user through the "Settings" panel in ruTorrent, are valid until rtorrent restart. After which all settings will be set according to the rtorrent config file (.rtorrent.rc).
- If numbers greater than 2Gb are shown as negative, rtorrent should be recompiled with a xmlrpc-c version 1.11 or later.
- If the port which rtorrent is listening for requests is changed, it is necessary to make appropriate changes in the ruTorrent configuration file (see ruTorrent config for more details) - set the same port number in
ruTorrent/conf/config.phpfor the variable$scgi_port. - As stated above, Authentication should be provided by web-server only and does not depend on ruTorrent. If authentication is necessary, make sure the webroot and the scgi mount point are both protected (if you mount the scgi directory in a subdirectory of the webroot, and enable authentication on the webroot, this is sufficent) If either the RPC or HttpRPC plugin is used, the scgi mountpoint (for example,
/RPC2) folder protection is not necessary. - If you are running a multi-user setup, each user should have a different scgi mountpoint. You can name these mountpoints anything you like, provided you change the configuration settings accordingly, for more info see ruTorrent config and Web Server Setup.
