Failed to connect to LDAP server

I'm having a series of LDAP issues after upgrading to Webmin 1.910.

I created a virtual server yesterday and got a bunch of LDAP errors. My backups are failing because of a bunch of LDAP errors. And when I go to delete any server in Virtualmin I get the following message:

Failed to connect to LDAP server localhost on port 389

I've gone to Webmin's LDAP Client. When I click "Validate Configuration" everything comes back good. I can even browse everything in LDAP Browser. So it appears Webmin is configured correctly and views records correctly, but still can't connect to the LDAP server.

Suggestions?

Status: 
Active

Comments

Are you using LDAP to store Unix users and groups? If so, does the module at Webmin -> System -> LDAP Users and Groups work for you?

That's a great question. Yes, Virtualmin users and groups are stored in LDAP and all of them are showing up. Including the user/group from the most recently created virtual server. Note that when I created the newest virt, it gave me a bunch of "can't connect to LDAP on port 389" errors.

Still getting LDAP errors when backing up. See below:

   Saving mail aliases ..
   .. backup of mail failed : Failed to connect to LDAP server localhost on port 389

I downgraded to Webmin 1.900. Fixed all my LDAP problems. Something is messed up in the 1.910 update.

Unusual that downgrading would help, as there hasn't been any changes in 1.910 related to how LDAP is used.

In theory...lol.

The only thing I did was downgrade to 1.900. I'm certain 1.910 caused the problem.

My guess is that it has nothing to do with LDAP and something to do with user and group management.

Where can I find the source for these two?

I'm reviewing the checkin history to see if anything stands out, but if you do some coding as well, you're quite welcome to take a peek... you can see the git checkins for Webmin here:

https://github.com/webmin/webmin/commits/master

Note that Webmin version 1.910 came out on May 9th, and version 1.900 came out on November 18th. So it could be something within that window.