I’ve run into this before, but have always been able to get it to work since I have always run the daemon and the web server on the same server, so the default localhost:58846 worked fine. However, I just setup my web server on a separate host from the daemon and could not get auto connect to work no matter what I tried. After some digging and looking at the actual Python code, I finally discovered how this works.
In the web.conf configuration file for the Deluge Web server, there is a line for “default_daemon” which can specify the default daemon. However, everyone on the web says to put the hostname:port here of the daemon you want to connect to. This is not correct. The value here is expected to be the host ID of the configured daemon. However, this info is not provided anywhere in the UI. After a little more digging I finally found the info needed.
Where the web.conf file resides, there is also a file called hostlist.conf.1.2. This file contains all of the configured daemons for the web server. Each host configured in this file should have a long string of characters as the first line in each definition. Here’s an example from my setup:
"a460f75d27562b0317a22b3e2600bd23e1fedb16", <- This is what you need
Now, make sure that your deluge web server daemon is shut down then edit the web.conf file and paste that host ID into the double quotes after “default_daemon”. Now start your deluge web service and it should automatically connect to the specified daemon.
I setup a Nextcloud server a few months back. I immediately enabled and configured encryption. I also keep daily file backups using rsync to a backup server. This backup does, of course, backup the encrypted versions of my files. Ever since setting this up, I’ve been trying to find a way to be able to restore an individual file from my backup, but until now I haven’t found a decent working solution. It seems, though, that I may have finally uncovered such a solution.
I had a personal blog hosted at www.jecal22.com, but decided that I really don’t use it anymore and preferred to have my tech blog hosted as the primary website. I’ve setup permanent forwards so any old links still using tech.jecal22.com will still work, but please note that the URL has indeed changed.
For at least the past decade you have been told not to enter any private or secure information on a website unless you saw the little padlock icon which indicated you were on a secure website. Over the last few years, and with different browsers sharing the internet browsing market, that little padlock has evolved into an even more noticeable indicator which is usually a color coded button near the address bar. Green means good, red means bad, right? Well, it’s not quite that simple. Continue reading
Project Fi has been around now for a little over a year now and has been gaining more and more popularity, especially among those who like to have Google’s flagship phones. I’ve personally been using Fi since August 2015, and I have to say that I’ve been overly impressed with all aspects of my experience from the phone itself to the reliability and flexibility of the service down to the support behind the service. My previous carrier, Sprint, was very disappointing in most of these aspects.