Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDAP bind failed immediately: Can't contact LDAP server #68

Open
lnredone opened this issue Aug 25, 2018 · 6 comments
Open

LDAP bind failed immediately: Can't contact LDAP server #68

lnredone opened this issue Aug 25, 2018 · 6 comments

Comments

@lnredone
Copy link

Why Centos 7.4 install OPENVPN 2.4.6 use OPENVPN - auth - ldap2.0.3. The correct RPM package
The same environment in centos6.5 no problem

LDAP bind failed immediately: Can't contact LDAP server

@colinbjohnson
Copy link

Two suggestions:

  1. Attempt to make the same connection using the ldapsearch utility.
  2. Include the conf file utilized by OpenVPN.

@netkey
Copy link

netkey commented Dec 18, 2018

I met the same problem,it works fine for serveral days,but today the vpn server can't work,it seems the openvpn server exited when can't connect to ldap server.

here is some log :

Dec 18 10:19:25 openvpn[1356]: LDAP bind failed immediately: Can't contact LDAP server
Dec 18 10:19:25 openvpn[1356]: Unable to bind as cn=Manager,dc=test,dc=com
Dec 18 10:19:25 openvpn[1356]: LDAP connect failed.
Dec 18 10:20:00 systemd[1]: openvpn@server.service: main process exited, code=killed, status=6/ABRT
Dec 18 10:20:00 systemd[1]: Unit openvpn@server.service entered failed state.
Dec 18 10:20:00 systemd[1]: openvpn@server.service failed.

@Soraphiroth
Copy link

I have the same issue, with CentOS 7.6, ovpn 2.4.6 and auth-ldap 2.0.3. I verified with ldapsearch and I get my results without any problem.

My solution was simply to use the IP of the domain controller. I don't know why but the plugin can't seem to find it with its fqdn or simply the domain.

@albert748
Copy link

The same issue here, looks like DNS resolver not stable, any update?

@psychomantys
Copy link

i have this problem when using chroot

@badsysadm
Copy link

i have this problem when using chroot

It looks like the chroot has an incorrect resolv.conf file or something like that. When accessing the ldap server via IP, everything worked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants