javax.net.ssl.SSLKeyException

FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web227

  • FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • via Google Groups by Gaurav Khanna, 1 month ago
    FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • via Google Groups by Mark, 1 month ago
    FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
  • Stack trace

    • javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received. at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(UnknownSource) at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(UnknownSource) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(UnknownSource) at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(UnknownSource) at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source) at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source) at com.certicom.tls.record.ReadHandler.interpretContent(Unknown Source) at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source) at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(UnknownSource) at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(UnknownSource) at com.certicom.tls.record.WriteHandler.write(Unknown Source) at com.certicom.tls.record.WriteHandler.write(Unknown Source) at com.sun.jndi.ldap.Connection.<init>(Connection.java:209) at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:108) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2379) at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:239) at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:74) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 11 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    5 more bugmates