The port will be the same as the port used by uTorrent for BT connections. I recommend setting a seperate port to be used for the WebUI, since the other port often changes randomly. The WebUI port can be set in the same part of settings as the username and password.

The hostname should be just xx.xx.xx.xx. The protocol is fixed, so there's no point in having a http:// there. If you have uTorrent running on a publicly accessible domain name (e.g. with DynDNS) then you can use the domain name. For LANs, I believe that WINS can be supported with the winbind package from extras-dev, however I wouldn't recommend it. Most people should be fine using the IP directly, though you can add it to the hosts file if it's a static IP and you use it a lot.

With regard to 'Enable Automatic Updates', this setting is disabled when an error ocurrs. If you aren't getting anything, check that it is enabled, and that you have All Torrents selected under Sorting/Filtering.

The password is stored in a plain text XML file somewhere in ~/.config/. I haven't encrypted it as uTorrent uses Basic authentication, so it's transmitted unencrypted anyway. Even if I did encrypt it, the key would have to be stored either in the executable or as a seperate file, and would be available as part of the source - if the (theoretical) attacker has access to the settings file they would have access to the key as well, making the encryption rather pointless. Given that uTorrent isn't so important as to require such security, I will be leaving it as it is. If you really are that paranoid, you can encrypt the file with TrueCrypt and the connection with OpenVPN.

At this stage I have no plans to implement support for other clients, as it significantly increases the complexity of the program, and I am unfamiliar with the protocols used by them. If there is sufficient demand I may do so at a later stage, though not any time soon. For those of you using Linux, uTorrent 1.8.5 runs fine under WINE.