- X-Pack Reference for 6.0-6.2 and 5.x:
- Introduction
- Setting Up X-Pack
- Breaking Changes
- X-Pack APIs
- Graphing Connections in Your Data
- Profiling your Queries and Aggregations
- Reporting from Kibana
- Securing the Elastic Stack
- Getting Started with Security
- How Security Works
- Setting Up User Authentication
- Configuring SAML Single-Sign-On on the Elastic Stack
- Configuring Role-based Access Control
- Auditing Security Events
- Encrypting Communications
- Restricting Connections with IP Filtering
- Cross Cluster Search, Tribe, Clients and Integrations
- Reference
- Monitoring the Elastic Stack
- Alerting on Cluster and Index Events
- Machine Learning in the Elastic Stack
- Troubleshooting
- Getting Help
- X-Pack security
- Can’t log in after upgrading to 6.2.4
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- X-Pack Watcher
- X-Pack monitoring
- X-Pack machine learning
- Limitations
- License Management
- Release Notes
WARNING: Version 6.2 of the Elastic Stack has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
SSLHandshakeException causes connections to fail
editSSLHandshakeException causes connections to fail
editSymptoms:
-
A
SSLHandshakeException
causes a connection to a node to fail and indicates that there is a configuration issue. Some of the common exceptions are shown below with tips on how to resolve these issues.
Resolution:
-
java.security.cert.CertificateException: No name matching node01.example.com found
-
Indicates that a client connection was made to
node01.example.com
but the certificate returned did not contain the namenode01.example.com
. In most cases, the issue can be resolved by ensuring the name is specified during certificate creation. For more information, see Setting Up TLS on a Cluster. Another scenario is when the environment does not wish to use DNS names in certificates at all. In this scenario, all settings inelasticsearch.yml
should only use IP addresses including thenetwork.publish_host
setting. -
java.security.cert.CertificateException: No subject alternative names present
-
Indicates that a client connection was made to an IP address but the returned certificate did not contain any
SubjectAlternativeName
entries. IP addresses are only used for hostname verification if they are specified as aSubjectAlternativeName
during certificate creation. If the intent was to use IP addresses for hostname verification, then the certificate will need to be regenerated with the appropriate IP address. See Setting Up TLS on a Cluster. -
javax.net.ssl.SSLHandshakeException: null cert chain
andjavax.net.ssl.SSLException: Received fatal alert: bad_certificate
-
The
SSLHandshakeException
indicates that a self-signed certificate was returned by the client that is not trusted as it cannot be found in thetruststore
orkeystore
. ThisSSLException
is seen on the client side of the connection. -
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
andjavax.net.ssl.SSLException: Received fatal alert: certificate_unknown
-
This
SunCertPathBuilderException
indicates that a certificate was returned during the handshake that is not trusted. This message is seen on the client side of the connection. TheSSLException
is seen on the server side of the connection. The CA certificate that signed the returned certificate was not found in thekeystore
ortruststore
and needs to be added to trust this certificate.