Messages

its not a new deployment, its already used in production on older 24.7 releases.

I planed to upgrade and thats the point where i cant because of an update that bricked something, and i am not alone.

With no encryption I cannot reproduce the problem with our test ldap, hopefully it is clear that you should not use it productively, the productive ldap is LDAPS only.



with LDAPS im getting exactly the same on our testing LDAP which speaks LDAPS as well as LDAP.
2025-04-14T10:46:48    Error    opnsense    LDAP bind error [; Can't contact LDAP server]

What do i need to provide so we can debug this more?

Hello,

is any one able to reproduce this by connecting with an LDAP Server using LDAPS (SSL)?
The LDAPS Server is using an Letsencrypt certificate, which is under the defaults of the OS (it was with OPNSense 24.7), i just added the CAs manually into the OPNsense Trust part, didnt change anything. i only get a working connection using no encryption, which is disabled on the production environment.

Else i may start opening a issue, since i guess its not only me.

its not a new deployment, its already used in production on older 24.7 releases.

I planed to upgrade and thats the point where i cant because of an update that bricked something, and i am not alone.

With no encryption I cannot reproduce the problem with our test ldap, hopefully it is clear that you should not use it productively, the productive ldap is LDAPS only.



with LDAPS im getting exactly the same on our testing LDAP which speaks LDAPS as well as LDAP.
2025-04-14T10:46:48    Error    opnsense    LDAP bind error [; Can't contact LDAP server]

What do i need to provide so we can debug this more?

I know of no directory that uses uid= in a distinguished name. What directory is this? Active Directory uses cn=xyz,ou=...,dc=domain,dc=com. Hence my suggestion.

The documentation uses cn=

its rfc2307bis openldap (slapd) and I think I know best which DN my binduser uses in LDAP, it's not as if opnsense is the first software to be connected via it.

well thats wrong, since thats not the bind dn, why should that work, older opnsense versions work with exact same settings. thats not a fix.

like that: `uid=testing-binder,ou=bindUsers,dc=somename,dc=net`

i have the same issue...