#How to use deluge client full

Slvrdragn wrote:Recently found this and trying ti out, for anyone trying to find a solution. I am trying to get this working on my Ubuntu 18.04 instance, and every time I run into an error as written above, and this is because deluge frontends communicate with deluged through a TCP port, and that isn't available outside of the protected namespace(if it where using a unix socket file instead, like rtorrent can for xmlrpc calls, then it would work without running in protected namespace, but deluge doesn't use that). There, fool-proof killswitch behaviour and split-tunnel, with only the need of downloading and running a single small python script, without any iptables rules to add, cron-jobs, ip-binds or anythingĮdit2: No longer untested The commands above works perfectly, and yes, the used UI interface needs to be also run from the protected namespace i.e.

#How to use deluge client full

Also, I used full path for the config in the namespaced-openvpn command, even though I had used a -cd command, but that was still needed to make it work and not an oversight ).

Code: Select all sudo systemctl stop standard systemd service file provided with openvpn adds '/etc/openvpn/client/' as working-folder by itself, so no need for '-cd' like the namespaced-openvpn command - if you have absolute path for your certificates and everything in your openvpn config file(pia.conf above), then you don't need the '-cd' command for namespaced-openvpn either, or if you cd to the folder first, you don't either.