Deluge

Cas wrote:Yes we have transitioned git, forum, and dev subdomains to https by default now.

The problem with download.deluge-torrent.org is that it is using our hosts cert. I will remind them again to look into that.

Can you remind them again? I's still invalid.

Do not pull from master as it is an old build.
Use either '1.3-stable' to get the latest 1.3 version (1.3.15 with some updates) or 'develop' to get the latest 2.0.0 beta.

Go to Preferences =>Interface.

This should be done automatically when adding the same torrent to Deluge and setting the download location to the same folder. This will make Deluge perform a recheck for the files. But if you are not trusting Deluge to do this, add the torrent in pause state and than right-click the torrent and sel...

Yes, the WebUI interface is now part of the develop branch as of 12th of July.

Try creating a new text file named "RELEASE-VERSION" and enter the value "2.0.0.dev7192" to it.

Try looking in the log file of deluge: ~/.config/deluge/deluged.log

can you check in the logs for any errors/exceptions?
the logs are located in ~/.config/deluge/

Does the webui connects to the daemon?
Do you see anything in the preferences? If no, and there is no data (and no plugin is enabled) then you to connect to the daemon.

redirect stdout: deluge-console "connect localhost:8080; info" > deluge.info pipe it to more/less: deluge-console "connect localhost:8080; info" | less deluge-console "connect localhost:8080; info" | more i used the connect command as my port is non-standard.