Older deluge clients refuse to connect to the newer server installations, I do not know if this is due to API changes or something else. Since general availability of the 2.x clients are not yet available for windows, I wonder if it is possible to use older clients just to add / control the turrets.
Any way to program an API converter to allow such interconnection? Just curious if someone has already looked into such a possibility, thanks.
Any way to allow deluge UI 1.3.x to talk to remote server running 2.x.x?
Re: Any way to allow deluge UI 1.3.x to talk to remote server running 2.x.x?
No, unfortunately there have been big backend and communication-protocol changes, which makes such interaction impossible, and no "api-converter" either I'm afraid.
Re: Any way to allow deluge UI 1.3.x to talk to remote server running 2.x.x?
Had the same issue, primary reason for running a local client was to forward magnet / regular torrents to the server without having to go through hoops to get them added via a web UI.
What worked for me was a chrome extension, such as Remote Deluge, which allowed me to forward the data to the server and lookup status without a full flagged 2.x client. Additional benefit is that it auto logins to the deluge server UI, making a full interface available with a single click.
What worked for me was a chrome extension, such as Remote Deluge, which allowed me to forward the data to the server and lookup status without a full flagged 2.x client. Additional benefit is that it auto logins to the deluge server UI, making a full interface available with a single click.
