mirror of
https://github.com/rakshasa/rtorrent.git
synced 2026-10-21 08:36:18 +00:00
Updated to rTorrent 0.9 settings
+5
-5
@@ -28,19 +28,19 @@ ProxyPass /RPC2 scgi://127.0.0.1:5000
|
|||||||
|
|
||||||
**rtorrent.rc**:
|
**rtorrent.rc**:
|
||||||
```ini
|
```ini
|
||||||
scgi_port = 127.0.0.1:5000
|
network.scgi.open_port = 127.0.0.1:5000
|
||||||
```
|
```
|
||||||
|
|
||||||
### Lighttpd:
|
### Lighttpd:
|
||||||
|
|
||||||
**rtorrent.rc**:
|
**rtorrent.rc**:
|
||||||
```ini
|
```ini
|
||||||
scgi_local = /home/user/rtorrent/rpc.socket
|
network.scgi.open_local = /home/user/rtorrent/rpc.socket
|
||||||
|
|
||||||
# Set correct access rights to the socket file ----------+
|
# Set correct access rights to the socket file ----------+
|
||||||
# so both, lighttpd and rtorrent, could perform |
|
# so both, lighttpd and rtorrent, could perform |
|
||||||
# read-write operations v
|
# read-write operations v
|
||||||
schedule = scgi_permission,0,0,"execute.nothrow=chmod,\"g+w,o=\",/home/user/rtorrent/rpc.socket"
|
schedule2 = scgi_permission,0,0,"execute.nothrow=chmod,\"g+w,o=\",/home/user/rtorrent/rpc.socket"
|
||||||
```
|
```
|
||||||
|
|
||||||
**lighttpd.conf**:
|
**lighttpd.conf**:
|
||||||
@@ -62,7 +62,7 @@ scgi.server = (
|
|||||||
|
|
||||||
**rtorrent.rc**:
|
**rtorrent.rc**:
|
||||||
```ini
|
```ini
|
||||||
scgi_port = 127.0.0.1:5000
|
network.scgi.open_port = 127.0.0.1:5000
|
||||||
```
|
```
|
||||||
|
|
||||||
**nginx.conf**:
|
**nginx.conf**:
|
||||||
@@ -110,7 +110,7 @@ Do not forget, that on http://localhost:8008/RPC2 you will not see anything (thr
|
|||||||
If any of your downloads have non-ascii characters in the filenames, you must also set the following in rtorrent.rc to force rtorrent to use the UTF-8 encoding. The XMLRPC standard requires UTF-8 replies, and rtorrent presently has no facilities to convert between encodings so it might generate invalid replies otherwise.
|
If any of your downloads have non-ascii characters in the filenames, you must also set the following in rtorrent.rc to force rtorrent to use the UTF-8 encoding. The XMLRPC standard requires UTF-8 replies, and rtorrent presently has no facilities to convert between encodings so it might generate invalid replies otherwise.
|
||||||
|
|
||||||
```
|
```
|
||||||
encoding_list = UTF-8
|
encoding.add = UTF-8
|
||||||
```
|
```
|
||||||
|
|
||||||
The web server will now route xmlrpc requests to rtorrent, which is listening only on connections from the local machine or on the local socket file. Also make sure the /RPC2 location is properly protected, and also name it differently to evade attackers probing for vulnerabilities.
|
The web server will now route xmlrpc requests to rtorrent, which is listening only on connections from the local machine or on the local socket file. Also make sure the /RPC2 location is properly protected, and also name it differently to evade attackers probing for vulnerabilities.
|
||||||
|
|||||||
Reference in New Issue
Block a user