terag1e

FWIW: I have never in my online experience spanning decades, seen the following: signed in as an authorized user (password, username (email)) having provided credentials. Do your thing - scroll through the blog, web-pages in the domain, etc. LOG-OFF SUCCESSFULLY - the screen even said so. Close the browser, re-open the browser, go to the web-page requiring some sort of sign-in ----- and, drum rollllllll --- you are STILL LOGGED IN! I'm sorry not even a 256 character password is going to work in that scenario. Looks like help is needed in a flawed rollout, even if it is to "a small percentage of our user base."

I got signed in, changed password and everything appears to work as intended. Whilst I was changing things, I also decided to change the email address associated with the account. Unfortunately I get caught up in a vicious circle - change email, requires to re-authenticate, which uses the old email, the screen says the email was changed, I get an email change notification at the new e-mail), but it will only accept my old credentials when re-logging in. Rinse and repeat. No joy.

And I may yet! I have quite a few VMs throughout the network, but right now it's a problem for days in the future (thin client)!!

One of the reasons I have stuck with the 1.3.15 version of deluge is its ability to use the thin client, which I far prefer over the web client. But progress moves on, and I far prefer having the port forwarding OpenVPN with PIA, so a small price to pay. (And the legacy servers are retiring at the end of the month!) I do have a question, however. I force upgraded the newest binhex image, set it up, everything works pretty spontaneously. Thanks for all the quick, hard work, binhex!! The connection to CA Toronto resulted in a port forward connection. I can see this through one of my torrent providers that reports back if your seed is port forwarded. On the thin client, I could press a button on the Network tab of Preferences to "Check Port", which would always show a green ball if the port was forwarded or a yellow triangle/exclamation if not. Since there is no thin client in this version of deluge, and the web client on Network tab of Preferences does not have this, just a filled in port number, my question is this: Is there a way to determine if port forward is active on the connection? Can I inspect either supervisord or through the console window for the docker to easily confirm port forwarding is active for the torrents in the client?

Mine is currently Key 6 in the config screen with a container variable: STRICT_PORT_FORWARD, but it is not a drop down selection. you have to actually type in the setting (yes or no). Don't know enough to know whether or not the Variable name needs to be the same, but mine is Variable name: Key 6. Re using the port forward endpoints, I have had success with STRICT_PORT_FORWARD = no, still using the Canadian servers that I knew were portforwarding before all this, but then manually entering the port forward port in the settings in my stand alone deluge gui app (not web-gui). The port is definitely not forwarded as I can check that on a torrent site that I have active torrents on and it displays whether or not the current connection is port forwarded (it's not). But my speeds don't appear to have taken a huge (or any) toll. But I also haven't taxed the client much in the last couple of months.