[Bug] - ldap: connection closed

[madic-creates]

Describe the bug
After running VersityGW for approximately 24 hours, it can't connect to the configured ldap directory anymore. After restarting the gateway, ldap connections are working again. When using an s3 compatible client, the following error appears in the versitygw log:

Internal Error, LDAP Result Code 200 "Network Error": ldap: connection closed

When this happens, the ldap server does not receive any requests

To Reproduce
Use LDAP authentication backend for at least 24 hours with the following environment variables configured:

VGW_IAM_LDAP_URL: ldap://lldap.authelia.svc.cluster.local.:3890
VGW_IAM_LDAP_BIND_DN: uid=test,ou=people,dc=example,dc=com
VGW_IAM_LDAP_BIND_PASS: SuperSecretLdapPass
VGW_IAM_LDAP_QUERY_BASE: ou=people,dc=example,dc=com
VGW_IAM_LDAP_OBJECT_CLASSES: person
VGW_IAM_LDAP_ACCESS_ATR: vgw-access-key
VGW_IAM_LDAP_SECRET_ATR: vgw-secret-key
VGW_IAM_LDAP_ROLE_ATR: vgw-role
VGW_IAM_LDAP_USER_ID_ATR: vgw-uid
VGW_IAM_LDAP_GROUP_ID_ATR: vgw-gid

Expected behavior
LDAP Backend just working

Server Version
Version : v1.0.16
Build : b2516e4
BuildTime: 2025-07-18T15:21:42Z
Linux versitygw-7ccdf489db-8rcfk 6.14.5-1-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.5-1~bpo12+1 (2025-05-21T15:55Z) x86_64 Linux

Additional context
Running as pod in a kubernetes cluster.
The full kubernetes deployment can be found here: https://github.com/madic-creates/k3s-git-ops/tree/main/apps/versitygw

Behavior is independent of used client (rclone, s3cmd, restic)

[benmcclelland]

@madic-creates Would you be able to test this branch/PR #1473 to see if this resolves the issue you are seeing? I don't have an easy way to reproduce this over here and validate the fix.