usernameispain

Ah so there we go, since jonathanm directed me to the FAQ which I should've found on my own really (ugh), I was able to access the daemon by another client. The client had the "Test Active Ports" button which told me it was all good!

Back again! New question, how do I connect an remote/external deluge client to the daemon that this image runs? Where do I find what IP to use and what is the usename/pass? (Would guess that the pass I changed to in the web-UI is correct, but username is still a mystery to me.

Might there be a console command? Gonna go search for such.

Yeah I've seen it before (when using non-web-UI client), but it isn't there now. Is it not a thing on the web-UI?

I'm running docker on Synology yes, I kinda know how the mapping works, I was just worried that mapping directories to the "made up" /music or /video directories might mess something up. Thanks for clearing that up Yeah it's all correctly assigned, private-tracker sites still tell me I'm connectable but multiple port-scanners don't. I'm confused.

But I am running it on the VPN assigned IP, not my ISPs, I'm running it on the IP that the torrents see.

The private trackers that I use seem to consider me "connectable", but any port-scanner tells me otherwise about the port I've set at the OVPN settings. The service is great, I recommend it, really. A bit pricier than other's but definitely worth the money imo. Additional question: If I want to add other shared folders to the docker container for deluge to access, can I just point them to '/data/*name of shared folder*'? For example: I've got the shared folder 'downloads' set to '/data' Can I set the shared folder 'video' and 'music' to '/data/video' and '/data/music' respectively? I want to be able to seed from other shared folders as well as the one set/directed to '/data', but docker doesn't allow me to set the Synology volume as a reference-point/folder.

Oh that makes sense, my provider is OVPN. My config is set to "custom" since "OVPN" didn't seem to work. I've already opened the port in question at their end too.

I went ahead and ONLY changed Deluge's "Incoming Ports" to the desired port. I then opened the port on my router (TCP/UDP). I still see nothing, when I port-check the external VPN address by that port it tells me it's closed.

I am not using PIA, I'm using another provider so my config is set to "custom". I only intend to open ports so that I'm connectable to private trackers, but the ports that are set by default in the container config/deluge-daemon can't be used by my provider so I need to change them to fit my providers restrictions. I just need confirmation of what I need to edit locally, is it just the deluge config and container ports that need to be changed or are there other configs that require the same edits? And secondly, may I ask which ports are responsible for "connectability" exactly, it's only the "incoming" port (58496) of the Network category, right? Many thanks for any answers, I really appreciate you taking the time to answer questions in these forums

Alright so I've got everything up and running, I've only got one problem, I can't use the ports provided. I thought I might mess things up by changing them myself everywhere I can find them, so I want to confirm with someone who knows where the ports need to be reconfigured for it to work fine again. All I can think of is to change the deluge-daemon and container ports accordingly to what ports I can utilize, is this correct or are there other configs to edit too that I just don't know about? This docker image is very useful, thanks!