This is something I just ran into recently. When trying to push Internet Settings via GPO, some settings do not seem to be pushed even though other settings are. For example, when trying to push proxy server settings, the checkbox to enable specifying a proxy server gets pushed to clients, but the proxy server address entered in the box does not. So the client ends up with the proxy option enabled, but a blank (or unchanged) server textbox.Continue reading
I just wanted to post an updated article about this awesome software. In case you have never heard of it, You Need A Budget (YNAB for short) is a browser based cloud app that helps you to budget your finances. It’s not your typical finance management application, though.Continue reading
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.
So you have a Sophos UTM device and want to setup dynamic DNS using your Google Domain? Sophos UTM offers a couple of built-in services for DynDNS, but Google Domains is not one of them. There are quite a few guides out there for hacking the UTM so that you can get this functionality, but they all seem to require creating a custom configuration file and then either manually starting the service at each boot, scheduling it to run, or something similar.
I recently upgraded two of my CentOS 6 VMs to CentOS 7.3. Both of these utilized ZFS. I installed ZFS using the repos from zfsonlinux.com as I have always done. I do always use the kmod version since I’ve had issues with the dkms version in the past when performing updates. I got my zpools imported just fine, but noticed that after rebooting that I would have to re-import them again. I started investigating this and eventually discovered such a simple solution.