Please note that not all authentication methods were available. Check the system log or Icinga Web 2 log for more information

We are currently experiencing an issue where we are unable to authenticate a particular domain, so users are unable to log in. We experienced an issue Sunday and Monday (yesterday and the day before) that due to bad formatting in Rancher/Kubernetes when modifying the roles.ini file, it caused Icinga to repeatedly encounter syntax errors, until we modified the yaml file.

Now, we are getting the following exception: Please note that not all authentication methods were available. Check the system log or Icinga Web 2 log for more information.

On Friday and Saturday last week, we did not have this issue for the particular domain experiencing the issue. After fixing the permissions related to the above with the bad formatting, users started experiencing this.

All that has changed is the correct formatting and adding back in the existing permissions and groups that originally existed.

Logs within /var/log/icinga2/ do not provide any particularly useful information, and do not seem to indicate any particular issue. However, when validating the configuration for the group and users, we are receiving the following: * Failed to successfully validate the configuration: LDAP bind ("CN=user,OU=location,OU=location / ***) to ldaps://servername.domain:3269 failed: Invalid credentials.

I have replaced the above domain CN/OU path with generic names, as well as ldaps, just for this post. Credentials have not changed, either. I reviewed the following topic but did not find it particularly helpful: All configured authentication methods failed. Please check the system log or Icinga Web 2 log for more information

Any assistance is welcome. Please and thank you.

  • Icinga Web 2 version - 2.11.4
  • Used modules and their versions (System - About) - Grafana, Icingadb, Monitoring
  • Web browser used - Chrome, Edge, etc
  • Icinga 2 version used (icinga2 --version) - 2.11.4
  • PHP version used (php --version) - 8.1.2-1ubuntu2.13
  • Server operating system and version - Ubuntu Linux

I think your ldap connection is no longer working. you can disable the ldap user/group backend then the error is gone, but you still need to figure out what’s wrong with your ldap settings…

I was able to figure it out finally. This was due to formatting. Essentially, the OU path was split, and Icinga was only seeing half of the path, as opposed to the whole path.