Troubleshooting - LDAP Server
To troubleshoot LDAP Server Monitor, follow the below steps:
1. Unable to connect to the server:
Check if the given Host Name / IP Address is correct.
Run the below command in Applications Manger installed server to ensure Host / IP Address is reachable.
ping <Host Name/IP Address>
Eg: ping apm-server
Check if the given Port is correct.
Retry with the "SSL is enabled" option set to both enabled and disabled states in the add/edit monitor page.
Run the below command in Applications Manager installed server to ensure service is running.
telnet <HostName> <Port>
Eg: telnet apm-server 80
New to ADSelfService Plus?
Related Articles
LDAP - Unable to find valid SSL Certificate
If there is an error while adding LDAP Server Monitor with the message "Unable to find valid SSL Certificate", then please try the below steps to troubleshoot the issue. When the error occurs we can find the below traces in the "stderr.txt.*" log ...Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the below steps for troubleshooting. Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer this help ...Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...Troubleshooting - Apache Server
Troubleshooting - Apache Server monitor If you're encountering issues in Apache Server monitor in Applications Manager, follow these steps to diagnose and resolve the problem: 1. Verify the Server is an Apache Server: Open Command Prompt on the ...Troubleshooting Server error responses
When encountering the following server error responses—Bad Gateway (502), Service Unavailable (503), and Gateway Timeout (504)—it typically indicates issues with the server hosting the URL. Troubleshooting Review your server's access logs for the 30 ...