PingDirectory

The server won’t accept client connections

Check the current server state by using the bin/server-state command. If the server doesn’t appear to be accepting connections from clients, reasons can include the following:

  • The server isn’t running.

  • The underlying system on which the server is installed isn’t running.

  • The server is running, but isn’t reachable as a result of a network or firewall configuration problem. If that is the case, connection attempts should time out rather than be rejected.

  • If the server is configured to allow secure communication through Secure Sockets Layer (SSL) or StartTLS, a problem with the key manager or trust manager configuration can cause connection rejections. Messages are written to the server access log for each failed connection attempt.

  • The server might have reached its maximum number of allowed connections. Messages should be written to the server access log for each rejected connection attempt.

  • If the server is configured to restrict access based on the address of the client, messages should be written to the server access log for each rejected connection attempt.

  • If a connection handler encounters a significant error, it can stop listening for new requests. A message should be written to the server error log with information about the problem. Restarting the server can also solve the issue. A third option is to restart the connection handler using the LDIF connection handler to make it available again. To do this, create an LDIF file that disables and then re-enables the connection handler, create the config/auto-process-ldif directory if it doesn’t already exist, and then copy the LDIF file into it.