You should consider looking into why the CLI is so laggy. Setting a parameter takes between 60 and 90 seconds. Normally a CLI is pretty snappy.

Any developers want to chime in on why this takes so long to return?

For those who come looking for answers, here's what I found to the best of my knowledge: CRON can run as either root or a specific user depending on how you set it up. I assumed that running it as root would give it permissions to access the deluge-daemon. It doesn't you have to setup the cron job t...

Were you able to solve this problem? I'm assuming cronie runs as root, which means it should execute commands as root.

I'm not sure if I solved this or not. I checked with my tracker and I'm connectable. Furthermore, I am able to upload now. However, my uploads SEEM to be much slower. So much so, that it appeared to me that I was unconnectable. However, after a few days, I logged some uploads.

I have a script that updates my deluge configuration with port information. I run the following command:
This takes beween 60-90 seconds. What's that about?

I use Private Internet Access as a VPN. When I was using uTorrent (older version without ads), I would get a port from PIA and enter that into the incoming connections box. It worked fine. I was able to receive incoming connections. I switched to Deluge on my PC and did the same thing, however, delu...

I spent all day trying to solve this problem: Installed deluged and deluge-web on archlinux Started and enabled both services Accessed the web UI and set the download location to a mounted NAS location The test torrent I loaded threw an error with: Permission denied: /home/admin/NAS_Public/Downloads...