From 68d130d1ea6b06bbb5f8c6a1b8ce583506ea96d6 Mon Sep 17 00:00:00 2001 From: Matthew Strasiotto <39424834+matthewstrasiotto@users.noreply.github.com> Date: Mon, 5 Jul 2021 09:45:28 +1000 Subject: [PATCH] Clean up my edits --- RPC-Setup-XMLRPC.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/RPC-Setup-XMLRPC.md b/RPC-Setup-XMLRPC.md index b655b2c..3736641 100644 --- a/RPC-Setup-XMLRPC.md +++ b/RPC-Setup-XMLRPC.md @@ -53,8 +53,9 @@ What you need: network.scgi.open_local = /home/user/rtorrent/rpc.socket # Set correct access rights to the socket file ----------+ -# so both, lighttpd and rtorrent, could perform | -# read-write operations v +# so both rtorrent & your reverse proxy can performed | +# read-write operations | +# but most users on the system can not v schedule2 = scgi_permission,0,0,"execute.nothrow=chmod,\"g+w,o=\",/home/user/rtorrent/rpc.socket" ``` @@ -69,11 +70,6 @@ SCGIMount /RPC2 socket_path ProxyPass /RPC2 scgi://socket_path ``` -**rtorrent.rc**: -```ini -network.scgi.open_port = 127.0.0.1:5000 -``` - ### Lighttpd: **lighttpd.conf**: @@ -101,7 +97,8 @@ scgi.server = ( ```conf # This webserver is actually in a container that only publishes 8080 (container) -> localhost:8080 (host) - +# IN reality, the http server should have TLS / SSL +# Achieving this with nginx, traefik, or the reverse proxy of your choice is well documented. server { listen 0.0.0.0:8080; error_log ${CONFIG_DIR}/nginx/nginx.error.log;