Thin client can't connect to server on a specific computer

[v4vendetta75005]

Hello,
I'm at my wits end on an issue I've encountered since yesterday.
Server : binhex/delugevpn docker (latest) on an ubuntu 24.04 host ==> server version is 2.2.0
Thin clients :

• Trireme on Android ==> connects to the server on local lan (192.168.1.0/24) and over internet

• Deluge thin client (v2.1.1) on computer 1 (windows 11 25H2) ==> connects to the server on local lan (192.168.1.0/24) and over internet

• Deluge thin client (v2.2.0) on computer 2 (ubuntu 24.04) ==> connects to the server on local lan (192.168.1.0/24) and over internet

• Deluge thin client (v2.1.1 and v2.2.0 tested) on computer 3 (windows 11 25H2) ==> can't connect to the server, either on local lan (192.168.1.0/24) or over internet but can connect through Web UI on 192.168.1.XXX:8112

When I fill in host/credentials in the connection manager on computer 3 and double click on the connection, I get a 10013 error message "An attempt was made to access a socket in a way forbidden by its access permissions".

If every thin client had the same error I would be looking on the server side but it's only one and the other windows computer, on the same network with the same windows and thin client version has no issue.

Has anyone ever encountered this issue ? I'd love not to have to reinstall my main computer to totally debug...

[ambipro]

This sounds like an odd situation. I'm not immediately struck with anything, but if you're using binhex's Docker container and other Windows 11 thin clients work, then it sounds like it might be an issue with the user you are using to log in, perhaps?

Are you using the same username and password on the thin client across all systems? If you open the file `auth` in your /config mount, you should see a list of users in plaintext.

Can you try the localclient user with its long hash-like password on the Windows machine you are having trouble connecting with and see? That user should have full admin permissions. The password is in plaintext despite it looking like an encrypted hash, FYI.