RonneBlaze

accessing the server via the server.local and not by ipaddress seems to have been the issue.. It connected when using server.local.

My server was linked and some is not unlinked, When trying to link i login to my account, I get to the screen were it lists my server to my account, And then it just sits at the "Performing actions" screen says to keep it open while we perform some actions. I have left it open for hours and hours.. and it never links.. I have uninstalled the plugin and reinstalled. nothing. I even rebooted my server and tried it again same thing... oddly enough I had to do the same thing to a second server that uses another account and it linked right away.

can you update the docker to the newest bot version 3.1.0?

has anyone tried protonvpn ? a friend recommended them for normal vpn use., not sure if they would work with this docker.

I just moved from the normal deluge to the vpn version I am running an older build binhex/arch-delugevpn:1.3.15_18_ge050905b2-1-04 because i still use the windows gui to connect to my server and there is no 2.0 windows client yet. On the non vpn build i could port forward 58846 to my internal ip and be able to access deluge from outside of my network.. now after moving to the vpn build i can no longer access the server from outside of my network. my unraid server is still the same so the port forwarding still should be good. During the setup i did miss changing the LAN_NETWORK variable to my correct local network, and that prevented me from being able to use the windows client to access the server, once i fixed that to the correct ip i can connect locally. is there anything i can do to be able to connect from out side of my unraid network?

Being able to add one drive at a time (unlike freenas) Some UI improvements.