LDAP debugging not possible within LXC container?
Author: rholighausCreated Sep 18, 2019Updated Jul 28, 2026
I'm running wekan as a snap app within an unprivileged LXC Ubuntu 19.04 disco container unter Proxmox PVE 5.3. It's running well but I can't manage to LDAP to work. Unfortunately, I cannot see what Wekan is actually sending / receiving to/from the Active Directory server, no matter what I put into my config.
Here is my config:
{
"default-authentication-method": "ldap",
"ldap-authentication": true,
"ldap-authentication-password": "xxxxxx",
"ldap-authentication-userdn": "CN=Administrator,CN=Users,DC=mydomain,DC=local",
"ldap-background-sync": true,
"ldap-basedn": "OU=SHK Benutzer,DC=mydomain,DC=local",
"ldap-default-domain": "mydomain",
"ldap-email-field": "mail",
"ldap-enable": true,
"ldap-fullname-field": "cn",
"ldap-host": "192.168.1.6",
"ldap-internal-log-level": "debug",
"ldap-log-enable": true,
"ldap-log-enabled": true,
"ldap-port": 389,
"ldap-reject-unauthorized": true,
"ldap-search-field": "sAMAccountName",
"ldap-sync-user-data-fieldmap": {
"cn": "name",
"mail": "email"
},
"ldap-user-authentication": true,
"ldap-user-authentication-field": "userPrincipalName",
"ldap-user-search-field": "sAMAccountName",
"ldap-user-search-scope": "sub",
"ldap-username-field": "sAMAccountName",
"loglevel": 5,
"port": 80,
"root-url": "http://192.168.100.129"
}In my syslog, all I can see is this when trying to login:
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [INFO] Init LDAP login "[email protected]"
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [WARN] Lookup for unset variable: INTERNAL_LOG_LEVEL
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [WARN] Lookup for unset variable: LDAP_USER_ATTRIBUTES
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [INFO] Init setup
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [INFO] Connecting "ldap://192.168.1.6:389"
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [DEBUG] connectionOptions{ url: 'ldap://192.168.1.6:389',
Sep 18 14:51:24 snaptest wekan.wekan[42496]: timeout: 10000,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: connectTimeout: 10000,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: idleTimeout: 10000,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: reconnect: true,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: log:
Sep 18 14:51:24 snaptest wekan.wekan[42496]: Logger {
Sep 18 14:51:24 snaptest wekan.wekan[42496]: domain: null,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: _events: {},
Sep 18 14:51:24 snaptest wekan.wekan[42496]: _eventsCount: 0,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: _maxListeners: undefined,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: _level: 30,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: streams: [ [Object] ],
Sep 18 14:51:24 snaptest wekan.wekan[42496]: serializers: null,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: src: false,
Sep 18 14:51:24 snaptest wekan.wekan[42496]: fields:
Sep 18 14:51:24 snaptest wekan.wekan[42496]: { name: 'ldapjs',
Sep 18 14:51:24 snaptest wekan.wekan[42496]: component: 'client',
Sep 18 14:51:24 snaptest wekan.wekan[42496]: hostname: 'snaptest',
Sep 18 14:51:24 snaptest wekan.wekan[42496]: pid: 43930 } } }
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [INFO] LDAP connected
Sep 18 14:51:24 snaptest wekan.wekan[42496]: [ERROR] InvalidCredentialsError: 80090308: LdapErr: DSID-0C09042F, comment: AcceptSecurityContext error, data 52e, v2580
Sep 18 14:51:24 snaptest wekan.wekan[42496]: I can take tcpdump logs and try to find out what Wekan sends to the directory server but that's kind of frustrating and there must be a better way. Any idea why I can't get decent log information?
Source: wekan/wekan