Just upgraded from 1.3.15. Is 2.1.1 stable on Windows?

[pronator]

I just today upgraded my server (running in a container) from 1.3.15 to 2.1.1. I must say it went incredibly easy and I am impressed. All my configs and torrents were migrated in 6 seconds. Well done.

The web UI worked a treat, no issues. But when I connected from Windows 2.1.1 in Thin Client mode, things got a little wonky. After a while all of the values in the Added column disappeared. Some of the columns were way too skinny to accommodate the text. So I shut down and reconnected, and the first reconnect took many seconds to load the UI (500 torrents) and didn't remember my column sizes. The second reconnect (to try to reproduce) was incredibly fast and everything looks perfect, just like I left it.

Am I imagining it, or is the Thin Client a little wonky on Windows? The 1.3.15 Windows client has been rock solid for years, but I just couldn't stomach continuing to run a 7-year-old Python container that I could no longer build.

[pronator]

And now, after 2 hours of being idle, I tried to resume a paused torrent, and nothing happens. I'm able to pause an active torrent, but it's still showing up in the Active filter under "States". Something is definitely out of sync here.

[ambipro]

I use the thin client on windows pretty much 24/7.

Initially, I did have to reset all my columns...but after it persisted across restarts and reconnectings.

Just to confirm, you said you upgraded your server AND installed 2.1.1 on your windows machine?

I've had no issues like you're describing, I have over 12.5k torrents loaded. It sounds like you may have ownership issues? Is the account you're connecting to the daemon with have full privileges?

[pronator]

Just to confirm, you said you upgraded your server AND installed 2.1.1 on your windows machine?

Right. I paused all torrents, upgraded the server to 2.1.1, made sure everything was working via the web, then installed 2.1.1 on Windows.

Is the account you're connecting to the daemon with have full privileges?

I believe so. I connect the thin client with the same username/password as I used to, and new torrents are downloading as the mapped Synology user. But there is one funny thing in the thin client UI, the new torrents show up as Owner "deluge" (the Synology username), and the migrated ones as "Admin" (there is no such Synology username).

2024-08-23 11_49_52-Deluge.png (5.87 KiB) Viewed 12928 times

Glad to hear the UI is solid for you. I just tried again, and everything is working perfectly, super fast startup, with all my columns, pause/resume working. Is there some sort of debug mode I could use if things go wonky again? I am a developer, so I could help fix it if I could diagnose it.

Thanks!

[ambipro]

I think you would want to turn logging mode to "DEBUG" on the container itself, with linuxserver and binhex's containers both support changing the logging mode via environmental variables, then the log files should just generate with that logging mode.

You can check the user accounts in the "Daemon" section of the preferences in the thin client.