---
title: The server won&#8217;t accept client connections
description: Diagnose why the PingDirectory server will not accept client connections, from a stopped server or network problem to SSL and connection limit issues.
component: pingdirectory
version: 11.1
page_id: pingdirectory:troubleshooting_the_pingdirectory_suite_of_products:pd_ds_server_will_not_accept_client_connections
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/troubleshooting_the_pingdirectory_suite_of_products/pd_ds_server_will_not_accept_client_connections.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: August 13, 2024
---

# The server won't accept client connections

You can first check the current server state by using the `bin/server-state` command. If the server doesn't appear to be accepting connections from clients, then potential reasons 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, then connection attempts should time out rather than be rejected.

* If the server is configured to allow secure communication via SSL or StartTLS, then a problem with the key manager and/or trust manager configuration can cause connections to be rejected. If that is the case, then messages should be written to the server access log for each failed connection attempt.

* If the server has been configured with a maximum allowed number of connections, then it can be that the maximum number of allowed client connections are already established. If that is the case, then 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, then messages should be written to the server access log for each rejected connection attempt.

* If a connection handler encounters a significant error, then it can stop listening for new requests. If this occurs, then a message should be written to the server error log with information about the problem. Another solution is to restart the server. 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.
