# Connection Failure Codes

> [HTML Version](connection_failure_codes.htm)

_Written May 2018_

To help with debugging failed connections, a connection failure code from the following table is included in the status text (XHTTPF\_GETSTSTXT) and ashnet.log file messages:

| **Code** | **Meaning / Description** |
|------|------|
| 0 | Sucess |
| **** | **Non-secure Connections** |
| 1 | empty hostname |
| 2 | DNS lookup failed |
| 3 | DNS timeout |
| 4 | Aborted by application. |
| 5 | Internal failure. |
| 6 | Connect Timed Out |
| 7 | Connect Rejected (or failed for some other reason) |
| 50 | HTTP proxy authentication failure. |
| 98 | Async operation in progress. |
| 99 | Product is not unlocked. |
| **** | **Secure Connections (SSL/TLS)** |
| 100 | TLS internal error. |
| 101 | Failed to send client hello. |
| 102 | Unexpected handshake message. |
| 103 | Failed to read server hello. |
| 104 | No server certificate. |
| 105 | Unexpected TLS protocol version. |
| 106 | Server certificate verify failed (the server certificate is expired or the cert's signature verification failed). |
| 107 | Unacceptable TLS protocol version. |
| 109 | Failed to read handshake messages. |
| 110 | Failed to send client certificate handshake message. |
| 111 | Failed to send client key exchange handshake message. |
| 112 | Client certificate's private key not accessible. |
| 113 | Failed to send client cert verify handshake message. |
| 114 | Failed to send change cipher spec handshake message. |
| 115 | Failed to send finished handshake message. |
| 116 | Server's Finished message is invalid. |




**History**

2018 May, A-Shell 6.4.1555, ASHNET 1.11.162:  Append Connection Failure Codes to the XHTTPF\_GETSTSTXT return string, as well as to ashnet.log, to assist with debugging failed connections