oweeya

From the looks of it I don't think it's the same problem as I never had seen the action(754): initial bind failed: in my error log. But I will try following the guides there to see if it fix the issue. And since I'm not using SAMBA nor Apache plus being new to this whole thing, my understanding with it could be wrong. Updates: Since I saw a post in somewhere (sorry I literally browse so much that I can't remember them all) mentioning that you don't actually need port 636 to make TLS connection since...

From the looks of it I don't think it's the same problem as I never had seen the action(754): initial bind failed: in my error log. But I will try following the guides there to see if it fix the issue. And since I'm not using SAMBA nor Apache plus being new to this whole thing, my understanding with it could be wrong. Updates: Since I saw a post in somewhere (sorry I literally browse so much that I can't remember them all) mentioning that you don't actually need port 636 to make TLS connection since...

From the looks of it I don't think it's the same problem as I never had seen the action(754): initial bind failed: in my error log. But I will try following the guides there to see if it fix the issue. And since I'm not using SAMBA nor Apache plus being new to this whole thing, my understanding with it could be wrong. Updates: Since I saw a post in somewhere (sorry I literally browse so much that I can't remember them all) mentioning that you don't actually need port 636 to make TLS connection since...

From the looks of it I don't think it's the same problem as I never had seen the action(754): initial bind failed: in my error log. But I will try following the guides there to see if it fix the issue. And since I'm not using SAMBA nor Apache plus being new to this whole thing, my understanding with it could be wrong. Updates: Since I saw a post in somewhere (sorry I literally browse so much that I can't remember them all) mentioning that you don't actually need port 636 to make TLS connection since...

Yes when not using TLS I have confirmed that I can contact LDAP server. Indeed the 10..0.2.4 is a typo my bad. As for firewall I have checked and all the ufw are in inactive status. Some updates, using openssl s_client -connect 10.0.2.4:389 -starttls ldap -showcerts I am able to see the certs I have created on the server.

Yes when not using TLS I have confirmed that I can contact LDAP server when not using TLS. Indeed the 10..0.2.4 is a typo my bad. As for firewall I have checked and all the ufw are in inactive status. Some updates, using openssl s_client -connect 10.0.2.4:389 -starttls ldap -showcerts I am able to see the certs I have created on the server.

As for the 10.0.2.2 in the error log I have no idea what it is. The VMs are connected using NAT Network on VirtualBox. Using openssl s_client -connect 10..0.2.4:636 returns 40D72BE5847F0000:error:8000006F:system library:BIO_connect:Connection refused:../crypto/bio/bio_sock2.c:125:calling connect() 40D72BE5847F0000:error:10000067:BIO routines:BIO_connect:connect error:../crypto/bio/bio_sock2.c:127: connect:errno=111

As for the 10.0.2.2 in the error log I have no idea what it is. The VMs are connected using NAT Network on VirtualBox