Page 1 of 1

Remote connection

Posted: Tue Mar 29, 2022 7:58 am
by Peter88
I'm easily confused.
I need to use a remote connection, so I have enabled the webui, I see the server address and port number.
I then go to another PC to login. When go through a similar process the server address is exactly the same?
I'm missing something?
My guess is that I add a connection? Invent a server name? User name and password? My first thought was that I am supposed to know this info... but am I supposed to just invent these details?
OR... I am way off and need to.....
What?

Thanks

Re: Remote connection

Posted: Tue Mar 29, 2022 10:48 am
by mhertz
There's some info here, though for Linux - please search Google for 'deluge thinclient' for elaboration.

https://dev.deluge-torrent.org/wiki/Use ... ThinClient

Anyway, In short, you need the IP(or domain name) of server(running deluged/deluge-web), port(default 58846 for deluged, and 8112 for deluge-web) and user/pass, which you invent/define('user:pass:10' as per link posted) in the 'auth' file of deluge user-profile dir('%appdata%\deluge' on windows - on Linux depends, often '/var/lib/deluge/.config/deluge' or '~/.config/deluge'). Also, need 'allow_remote' to 'True', e.g in 'core.conf' of deluge profile dir(change this with 'deluged' stopped), or defined under deluge preferences(I believe is under web-UI atleast, if remember right).

Not very beginner friendly I can relate, and probably also easier to setup than my small writeup above, I mean doing from GUI instead maybe, but that is how I've always done atleast.

Good luck :)

Edit: If only for web-UI, then you don't need user/pass in 'auth', only ip/port and web-UI password('deluge' by default) + enabled 'Allow remote connections" in web-UI preferences - atleast if remember right, roughly a year ago when I tested that 'auth' wasent used here(well, localclient authentication from it, behind scenes, i'd technically gather/guess)