There is no issue, it's just a display conundrum. The single proxy (reflected by 'peer') now applies to all types. In order to fix a more serious issue with proxy not being set I thought it better to reset the other unused entries to none, however since this causes more confusion I shall instead mirror the peer setting across all of them.
Complete uninstall/reinstall and configure of Deluge on system. Only PEER settings are saved under PROXY (WebSeed/Tracker/DHT settings does save).
Just looking for confirmation WebSeed/Tracker/DHT settings are using PROXY please.
Cas wrote:There is no issue, it's just a display conundrum. The single proxy (reflected by 'peer') now applies to all types. In order to fix a more serious issue with proxy not being set I thought it better to reset the other unused entries to none, however since this causes more confusion I shall instead mirror the peer setting across all of them.
I'm using linux, but after updating to 1.3.14, I encountered the same issue. I found the references to this change but I'm still not sure the settings are being applied properly.
After setting the proxy, while a check my torrent IP came back correct, I was able to see by using tcpdump that my system was communicating direct with the peers listed in each active torrent. I was only after installing ltconfig and setting 'force_proxy' that all traffic began going only to my proxy ip.
And now I just found that after a restart of the deluged service, the force proxy setting reverted so i was back to peer to peer.