Title: Debugging
Last modified: September 19, 2017

---

# Debugging

 *  [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * (@yoursql719)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/)
 * Hi,
 * is there any possibility to debug wpdirauth in a deeper way than the general 
   debug function of wordpress?
 * My problem is that I get a wrong password message at ldap authentification with
   your plugin and this problem occurs only at one site within the whole multisite,
   while all other sites are running well. I don´t know which setting can corrupt
   this authentification method. Plugins or theme doesn´t seem the problem, because
   I deactivated all of these and it doesn´t work.
 * Can you give me a hint, what setting could cause this behaviour? I´ve exported
   the whole site and imported it to another multisite, I´ve imported it to a single
   site, but problem occurs.
 * Wpdirauth doesn´t seem to really send any ldap command out, because there are
   no ldap login failure logs at the ldap server.
 * Regards,
    -  This topic was modified 8 years, 8 months ago by [benhartwich](https://wordpress.org/support/users/yoursql719/).
    -  This topic was modified 8 years, 8 months ago by [benhartwich](https://wordpress.org/support/users/yoursql719/).

Viewing 8 replies - 1 through 8 (of 8 total)

 *  Plugin Author [Paul Gilzow](https://wordpress.org/support/users/gilzow/)
 * (@gilzow)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510052)
 * That’s odd. So, one site, for one user fails authentication? Or is the prebind
   failing, but only for one site?
 *  Thread Starter [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * (@yoursql719)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510078)
 * It´s one wordpress site. Login via wp-admin is not possible. It seems that there
   ´s no bind. All other wordress sites within the same multisite works.
 * For example:
    Error site: test.de/xy/wp-admin fails Other sites: test.de/cd/wp-
   admin works.
 *  Plugin Author [Paul Gilzow](https://wordpress.org/support/users/gilzow/)
 * (@gilzow)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510097)
 * So for test.de/xy/wp-admin wpDirAuth doesn’t appear to be working at all? Or 
   are you receiving an error message?
 * Since this is a multisite, do you have wpDirAuth network enabled? Or is it enabled
   on a site-by-site basis?
 *  Thread Starter [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * (@yoursql719)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510122)
 * It doesn´t work it all. Error Message: your password is not correct.
 * At both multisites wpdirauth is network enabled.
 *  Plugin Author [Paul Gilzow](https://wordpress.org/support/users/gilzow/)
 * (@gilzow)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510171)
 * on the test.de/xy/ site, is the error message:
 * `wpDirAuth Directory Authentication Error: Could not authenticate user. Please
   check your credentials.`
 * or is it
 * `Your password is incorrect`
 * ?
 * If it’s the second one, then wpDirAuth isn’t running at all, OR, it doesn’t see
   the account requesting authentication as being an ldap-authenticated account.
 * Is this happening for *every* ldap-authenticated user on test.de/xy/ or only 
   certain users?
 *  Thread Starter [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * (@yoursql719)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510229)
 * It´s the first one.
    It happens with every user, which uses ldap.
 *  Plugin Author [Paul Gilzow](https://wordpress.org/support/users/gilzow/)
 * (@gilzow)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9510903)
 * i’ve never seen a situation where it didnt work in a single instance of a multisite,
   but did for all the others. This is really… odd. To get a **wpDirAuth** error
   message that user auth failed the binding attempt had to fail. How the bind attempt
   happens depends on your LDAP setup.
 * There is a separate failure message of `Could not authenticate user.` but the
   title should be `WordPress Login Error` not `wpDirAuth Directory Authentication
   Error`.
 * So I just want to make sure you’re seeing the wpDirAuth title on the error message.
   I’m sorry about clarifying so much but getting a **wpDirAuth** auth failed message
   for every ldap-authed user but _only_ for one site in a multisite would be highly
   unusual.
 * Also, are you up-to-date on WordPress version and wpDirAuth? Also, are there 
   any plugins in use on this site and not the others that are working? Even plugins
   that you wouldn’t think could affect it.
 *  Thread Starter [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * (@yoursql719)
 * [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9519858)
 * Hi,
 * sorry for my late reply. Here the full login error message:
    “ERROR: The password
   you entered for the username xy is incorrect. Lost your password?”
 * My wordpress and your plugin are up to date. It seems to be a problem with my
   theme. Is there a good way to debug?
 * Regards,

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Debugging’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wpdirauth.svg)
 * [wpDirAuth](https://wordpress.org/plugins/wpdirauth/)
 * [Support Threads](https://wordpress.org/support/plugin/wpdirauth/)
 * [Active Topics](https://wordpress.org/support/plugin/wpdirauth/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpdirauth/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpdirauth/reviews/)

## Tags

 * [debugging](https://wordpress.org/support/topic-tag/debugging/)

 * 8 replies
 * 2 participants
 * Last reply from: [benhartwich](https://wordpress.org/support/users/yoursql719/)
 * Last activity: [8 years, 8 months ago](https://wordpress.org/support/topic/debuggin/#post-9519858)
 * Status: not resolved