Connect Windows 2.1 client to Docker

[D16Z5]

Hello

I installed Deluge on my Synology NAS using this tutorial, creating a Docker.
https://mariushosting.com/how-to-instal ... ology-nas/

I got everything figured out with the shared folders and stuff (fairly new to the NAS world) and it is downloading and seeding torrents just fine (seeding doesn't work with VPN on, but that's for another time) and can see everything on the WebUI.

Now I am stuck on the next step: connection to the daemon from the Windows client.

Anyone got any tips on what to investigate next?
Thanks.

Deluge on NAS: 2.1.1

Webui.jpg (21.73 KiB) Viewed 42564 times

Web settings.jpg (24.07 KiB) Viewed 42564 times

Deluge on Windows: 2.1.1

Windows settings.jpg (28.64 KiB) Viewed 42564 times

[mhertz]

You need the daemon port e.g default 58846 forwarded also, so edit your docker config for deluge, or recreate, with e.g added '-p 58846:58846 \'. Then add a new user in deluge too(as deluged and gtk-ui isn't run from same user normally, which the localclient method expects). It's supported doing such in GTK-UI also, like normally often done in auth file of config-folder, e.g test:test:10 on there, but as said, can be done from GUI too(as tricky otherwise on synology I believe, if remember right, editing config files I mean).

Edit: Sorry some parts above not thought through lol Add user from web-ui if possible there, or just edit auth in config dir, which should be easy for you when using docker and not straight syno package, unless mistaken. And enable allow_remote in core.conf of config-dir(of docker deluge, not local deluge), or do from web-ui if possible. Then can connect through gtk-ui when having forwarded 58846 in docker setup, restart it first to make sure.

[D16Z5]

Seems all I needed to do was to forward the port in the Docker container!

-p 58846:58846

Thanks so much, happy new year!

[mhertz]

Thanks buddy, happy new year you too!

[D16Z5]

After switching to a different Docker setup I got everything set up again, but once again the final step is connecting the Windows client.

I now get this:

Web settings new.jpg (14.43 KiB) Viewed 42404 times

Successful connection and can see all my torrents




-

Windows settings new.jpg (27.33 KiB) Viewed 42404 times

Windows password.jpg (11.63 KiB) Viewed 42404 times

Daemon is online but I cannot login.
I checked the password, I used to same as the Webui password....but it won't let me login


NOTE: I purposely changed the port to 58847, the container is forwarding 58846 to 58847

PS: I struggle to find any logs, where do I need to look?

[ambipro]

Not sure if this is the case, but you'll need to go to edit and enter your password and save it there, when it prompts you for the password connect it will not save or work properly.

A minor bug.

Also if you haven't setup an actual user in the auth file or "Daemon" preferences, you will need to do that.

The WebUI is not the same as the users for RPC daemon.

You should also add another user, not use localclient.

[D16Z5]

Not sure if this is the case, but you'll need to go to edit and enter your password and save it there, when it prompts you for the password connect it will not save or work properly.

This did not work

Also if you haven't setup an actual user in the auth file or "Daemon" preferences, you will need to do that.

The WebUI is not the same as the users for RPC daemon.

You should also add another user, not use localclient.

This worked, thanks!!

[ambipro]

No problem, glad you got it resolved :)