ldap_connect(): Could not create session handle:

This shouldn’t be related to the browser in use. Line 378 is where the plugin sets up the connection to ldap. What do you have entered for your Directory Servers (Domain Controllers) in the settings?

• This reply was modified 6 years, 6 months ago by Paul Gilzow.

ed165addc1.fayette.ketsds.net, ed165adgc1.fayette.ketsds.net

I think you might have found a bug. Can you try this version and let me know if it corrects the issue you’re seeing?

https://gist.github.com/gilzow/c777c142310b7f7d48d3110c6dc78974

It’s still not logging me in. However, there aren’t any new errors appearing on the debug.txt file. Should I expect there to be if the same problem persisted?

if you aren’t seeing errors in the debug.log/txt file, then we corrected that issue. What error message(s) are you seeing when you attempt to authenticate?

ERROR: Cookies are being blocked or not supported by your browser. You must enable cookies to use WordPress.

But I checked. The cookies are enabled.

ok, that sounds like a mismatch between the cookiedomain and the site domain. In your multisite set-up are you doing a domain-based multisite (each site has its own domain) or a directory-based multisite (each site is a subdirectory of a single domain)? If it is multiple independent domains, I actually wrote a blog post about it and the “cookies are blocked” issue: https://www.gilzow.com/blog/2017/02/20/multiple-independent-subdomains-in-a-wordpress-network/

I’m doing the sub-directories (www.example.com/blogsite01).

wpDirAuth doesn’t set the cookies, only adjusts the length of the cookie expiration via the filter auth_cookie_expiration. Do you have any other plugins related to authentication?

Unfortunately, the cookie error is a common issue when setting up a multisite. Try creating a local test user, disable my plugin and see if you still get the same cookie error when logging into the local user account.

In the mean time, I’ll add the fix from the test version above to the plugin and get it pushed out officially.

The only plugins that are network activated are:

Akismet
Multisite Enhancements
WordPress Importer
WpDirAuth

The head website at which everyone should log in has the following activated:

ARVE Advanced Responsive Video Embedder
Buttons X – lite
LoginPress – Customizing the WordPress Login

I tried using the admin login (the original login created when you first install WordPress) on Chrome and IE and I’m getting the same error. I guess it doesn’t have anything to do with your plugin. I wonder what’s going on.

• This reply was modified 6 years, 6 months ago by andre.thomas.

I found the answer. I’m sorry for taking up your time. At least you were able to find a bug!

All I had to do was add the following lines to the config file:

define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', ''); 

Now it works on both browsers. See the link below for more details.

wordpress.stackexchange.com – Cookie Issue

Glad you were able to track it down. Let me know if you need help with anything else.

Will do. I appreciate your customer service, prompt replies and willingness to help.