If you installed Deluge daemon with VPN Split Tunnel by following our guide, then you are running Deluge daemon as vpn user.Ĭhoose a username and password you will use to access Deluge daemon from the client, replace accordingly sudo echo username: password > /home/vpn/.config/deluge/auth Deluge Daemon Installed as vpn User for Split Tunneling On Ubuntu Server starting from version 15.04 with sudo systemctl start deluged Option 2. Now start the Deluge daemon service, on Ubuntu Server up to 14.04 LTS with sudo service deluged start Next step is to enable and allow remote connection for the Deluge daemon, open the nf file for editing sudo nano /home/deluge/.config/deluge/nf If you installed Deluge following our guide then you are running Deluge with user deluge.Ĭhoose a username and password you will use to access Deluge daemon from the client, replace accordingly sudo echo " username: password:10" > /var/lib/deluge/.config/deluge/auth If you have installed Deluge Daemon with VPN Split Tunneling, then proceed to Option 2.If you installed Deluge Daemon as deluge user, then proceed to Option 1. We will set it to level 10, admin, which will give the client user full control over Deluge daemon. The authentication level is a work in progress feature in Deluge 1.3.3 and it doesn't do anything yet, but it will be activated in an upcoming version. The auth file consists of a line with a username, a password, and the authentication level associated with the client. If you are running a version of Ubuntu Server equal or higher then 15.04 (that use systemd), then stop Deluge with sudo systemctl stop deluged If you are using an Ubuntu Server version up to 14.04 LTS (that use upstart script), then stop Deluge with sudo service deluged stop We need to edit the authentication file of the daemon. First we need to create a username and password for the client that will access the daemon. Once you have a working Deluge daemon that you can access over Deluge Web UI you can proceed with the ThinClient setup. Install Deluge daemon following our guide Install Deluge on Ubuntu Server 14.04 LTS or Install and Configure Deluge VPN Split Tunneling Ubuntu 14.x. All that is easily configured in docker without going through complicated routing and firewall configuration.Configure Deluge Daemon for ThinClient use Should the VPN go down or offline qBittorent is blocked. In my case, I have my qBittorent container dependent on the nordvpn container and all traffic in and out of qBittorent is forced through nordvpn. non-volatile filesystems as filesystems that are within the container are destroyed if the container is updated so anything that should be permanent, (like media files systems or the sonarr configuration filesystem) should be on the host server and mounted by the docker container so even if you delete the container these file systems persist.Īnother advantage that docker has is since it has its own network layer you can force your BitTorrent traffic through a VPN and let other things go out normally. You do need to make sure that you are aware of volatile vs. The nice thing that docker solves is program dependencies as the containers are preconfigured with things like mono, databases, etc that are needed by the application. I have one sonarr container, one radarr container, one sabnzbd container, one jacket container etc. Docker is a virtualization engine that runs applications in docker containers. Ummm… I am not sure what you mean by having multiple “dockers” such as indexer, media server, downloader etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |