Did Something Change/Break w/1.3.14 & Proxies?
Posted: Wed Mar 08, 2017 2:25 pm
I'm running headless as a service on Ubuntu 16.04 with clients on Windows 10 and OSX.
Since the daemon-side update to 1.3.14, something seems to have changed with proxy config. The only type of proxy that will change/save is Peer. Web Seed, Tracker, and DHT are all blank and stay blank. If I make a change to Peer it does update core.conf and the change does appear effective so I don't believe it's anything screwy with permissions to the conf files. However no matter what I choose/enter for the other types, those entries in core.conf stay empty. I even killed the daemon, manually updated core.conf to duplicate Peer's config to the other types, but when I started the daemon backup the settings reverted.
I've rolled the Ubuntu side back to 1.3.12 and left the clients on 1.3.14 and everything appears to be working normally again. I don't believe it matters, but the type were all Socks5 W/ Auth.
Since the daemon-side update to 1.3.14, something seems to have changed with proxy config. The only type of proxy that will change/save is Peer. Web Seed, Tracker, and DHT are all blank and stay blank. If I make a change to Peer it does update core.conf and the change does appear effective so I don't believe it's anything screwy with permissions to the conf files. However no matter what I choose/enter for the other types, those entries in core.conf stay empty. I even killed the daemon, manually updated core.conf to duplicate Peer's config to the other types, but when I started the daemon backup the settings reverted.
I've rolled the Ubuntu side back to 1.3.12 and left the clients on 1.3.14 and everything appears to be working normally again. I don't believe it matters, but the type were all Socks5 W/ Auth.