The following are possible Webhook errors you may encounter.
| Code | Response |
|---|---|
| 1 | The URL you provided is not support. |
| 2 | Initialization failed. |
| 3 | The URL was not properly formatted. |
| 5 | Couldn't resolve proxy. The given proxy host could not be resolved. |
| 6 | Couldn't resolve host. The given remote host was not resolved. |
| 7 | Failed to connect to host or proxy. |
| 8 | After connecting to a FTP server, a certain reply is expected back. This error code implies that it got a strange or bad reply. The given remote server is probably not an OK FTP server. |
| 9 | We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory. |
| 11 | After having sent the FTP password to the server, a proper reply is expected. This error code indicates that an unexpected code was returned. |
| 13 | Failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. The server is flawed.AW |
| 14 | FTP servers return a 227-line as a response to a PASV command. The line was not returned back. |
| 15 | An internal failure to lookup the host used for the new connection. |
| 17 | Received an error when trying to set the transfer mode to binary or ASCII. |
| 18 | A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size. |
| 19 | This was either a weird reply to a 'RETR' command or a zero byte transfer complete. |
| 21 | When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command. |
| 23 | An error occurred when writing received data to a local file, or an error was returned from a write callback. |
| 25 | Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server's explanation for this. |
| 26 | There was a problem reading a local file or an error returned by the read callback. |
| 27 | A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs. |
| 28 | Operation timeout. The specified time-out period was reached according to the conditions. Typically 1 second to resolve the host and 5 seconds to get a response back. |
| 30 | The FTP PORT command returned error. This mostly happens when you haven't specified a good enough address. |
| 31 | The FTP REST command returned error. This should never happen if the server is sane. |
| 33 | The server does not support or accept range requests. |
| 34 | This is an odd error that mainly occurs due to internal confusion. |
| 35 | A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others. |
| 36 | Attempting FTP resume beyond file size. |
| 37 | A file given with FILE:// couldn't be opened. Most likely because the file path doesn't identify an existing file. Did you check file permissions? |
| 38 | LDAP cannot bind. LDAP bind operation failed. |
| 39 | LDAP search failed. |
| 42 | Aborted by callback. A callback returned "abort". |
| 43 | Internal error. A function was called with a bad parameter. |
| 45 | Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections' source IP address. |
| 47 | Too many redirects. Typically set to a max of 10 redirects. |
| 48 | An option set was not recognized/known. |
| 49 | A telnet option string was Illegally formatted. |
| 51 | The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK. |
| 52 | Nothing was returned from the server, and under the circumstances, getting nothing is considered an error. |
| 53 | The specified crypto engine wasn't found. |
| 54 | Failed setting the selected SSL crypto engine as default! |
| 55 | Failed sending network data. |
| 56 | Failure with receiving network data. |
| 58 | Problem with the local client certificate. |
| 59 | Couldn't use specified cipher. |
| 60 | Peer certificate cannot be authenticated with known CA certificates. |
| 61 | Unrecognized transfer encoding. |
| 62 | Invalid LDAP URL. |
| 63 | Maximum file size exceeded. |
| 64 | Requested FTP SSL level failed. |
| 65 | When doing a send operation had to rewind the data to retransmit, but the rewinding operation failed. |
| 66 | Initiating the SSL Engine failed. |
| 67 | The remote server denied to login |
| 68 | File not found on TFTP server. |
| 69 | Permission problem on TFTP server. |
| 70 | Out of disk space on the server. |
| 71 | Illegal TFTP operation. |
| 72 | Unknown TFTP transfer ID. |
| 73 | File already exists and will not be overwritten. |
| 74 | This error should never be returned by a properly functioning TFTP server. |
| 75 | Character conversion failed. |
| 76 | Caller must register conversion callbacks. |
| 77 | Problem with reading the SSL CA cert |
| 78 | The resource referenced in the URL does not exist. |
| 79 | An unspecified error occurred during the SSH session. |
| 80 | Failed to shut down the SSL connection. |
| 81 | Socket is not ready for send/recv wait till it's ready and try again. |
| 82 | Failed to load CRL file |
| 83 | Issuer check failed |
| 100 | Continue) This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue). |
| 101 | (Switching Protocols) This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so. |
| 102 | (Processing) As a WebDAV request may contain many sub-requests involving file operations, it may take a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet. This prevents the client from timing out and assuming the request was lost. |
| 200 | (OK) Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action. |
| 201 | (Created) The request has been fulfilled and resulted in a new resource being created. |
| 202 | (Accepted) The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. |
| 203 | (Non-Authoritative Information) The server successfully processed the request, but is returning information that may be from another source. |
| 204 | (No Content) The server successfully processed the request, but is not returning any content. Usually used as a response to a successful delete request. |
| 205 | (Reset Content) The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view. |
| 206 | (Partial Content) The server is delivering only part of the resource due to a range header sent by the client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. |
| 207 | (Multi-Status) The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made. |
| 208 | (Already Reported) The members of a DAV binding have already been enumerated in a previous reply to this request, and are not being included again. |
| 226 | (IM Used) The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. |
| 300 | (Multiple Choices) Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation. |
| 301 | (Moved Permanently) This and all future requests should be directed to the given URI. |
| 302 | (Found) This is an example of industry practice contradicting the standard. |
| 303 | (See Other) The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message. |
| 304 | (Not Modified) Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-Match. This means that there is no need to retransmit the resource, since the client still has a previously-downloaded copy. |
| 305 | (Use Proxy) The requested resource is only available through a proxy, whose address is provided in the response. Many HTTP clients do not correctly handle responses with this status code, primarily for security reasons. |
| 306 | (Switch Proxy) No longer used. Originally meant "Subsequent requests should use the specified proxy." |
| 307 | (Temporary Redirect) In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For instance, a POST request should be repeated using another POST request. |
| 308 | (Permanent Redirect) The request, and all future requests should be repeated using another URI. 307 and 308 parallel the behaviours of 302 and 301, but do not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly. |
| 400 | (Bad Request) The request cannot be fulfilled due to bad syntax. |
| 401 | (Unauthorized) Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication. |
| 402 | (Payment Required) Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. As an example of its use, however, Apple's defunct MobileMe service generated a 402 error if the MobileMe account was delinquent. In addition, YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPTCHA. |
| 403 | (Forbidden) The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g. a recognized user attempting to access restricted content). |
| 404 | (Not Found) The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible. |
| 405 | (Method Not Allowed) A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource. |
| 406 | (Not Acceptable) The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request. |
| 407 | (Proxy Authentication Required) The client must first authenticate itself with the proxy. |
| 408 | (Request Timeout) The server timed out waiting for the request. According to W3 HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time." |
| 409 | (Conflict) Indicates that the request could not be processed because of conflict in the request, such as an edit conflict in the case of multiple updates. |
| 410 | (Gone) Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead. |
| 411 | (Length Required) The request did not specify the length of its content, which is required by the requested resource. |
| 412 | (Precondition Failed) The server does not meet one of the preconditions that the requester put on the request. |
| 413 | (Request Entity Too Large) The request is larger than the server is willing or able to process. |
| 414 | (Request-URI Too Long) The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. |
| 415 | (Unsupported Media Type) The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. |
| 416 | (Requested Range Not Satisfiable) The client has asked for a portion of the file, but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file. |
| 417 | (Expectation Failed) The server cannot meet the requirements of the Expect request-header field. |
| 418 | (I'm a teapot) This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. |
| 419 | (Authentication Timeout) Not a part of the HTTP standard, 419 Authentication Timeout denotes that previously valid authentication has expired. It is used as an alternative to 401 Unauthorized in order to differentiate from otherwise authenticated clients being denied access to specific server resources[citation needed]. |
| 420 | (Method Failure) Not part of the HTTP standard, but defined by Spring in the HttpStatus class to be used when a method failed. |
| 420 | (Enhance Your Calm) Not part of the HTTP standard, but returned by the Twitter Search and Trends API when the client is being rate limited. Other services may wish to implement the 429 Too Many Requests response code instead. |
| 422 | (Unprocessable Entity) The request was well-formed but was unable to be followed due to semantic errors. |
| 423 | (Locked) The resource that is being accessed is locked. |
| 424 | (Failed Dependency) The request failed due to failure of a previous request (e.g. a PROPPATCH). |
| 425 | (Unordered Collection) Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol". |
| 426 | (Upgrade Required) The client should switch to a different protocol such as TLS/1.0. |
| 428 | (Precondition Required) The origin server requires the request to be conditional. Intended to prevent "the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict." |
| 429 | (Too Many Requests) The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes. |
| 431 | (Request Header Fields Too Large) The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large. |
| 444 | (No Response) Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection (useful as a deterrent for malware). |
| 449 | (Retry With) A Microsoft extension. The request should be retried after performing the appropriate action. |
| 450 | (Blocked by Windows Parental Controls) A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage. |
| 451 | (Unavailable For Legal Reasons) Defined in the internet draft "A New HTTP Status Code for Legally-restricted Resources". Intended to be used when resource access is denied for legal reasons, e.g. censorship or government-mandated blocked access. A reference to the 1953 dystopian novel Fahrenheit 451, where books are outlawed. |
| 451 | (Redirect) Used in Exchange ActiveSync if there either is a more efficient server to use or the server can't access the users' mailbox. The client is supposed to re-run the HTTP Autodiscovery protocol to find a better suited server. |
| 494 | (Request Header Too Large) Nginx internal code similar to 413 but it was introduced earlier. |
| 495 | (Cert Error) Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection. |
| 496 | (No Cert) Nginx internal code used when client didn't provide certificate to distinguish it from 4XX in a log and an error page redirection. |
| 497 | (HTTP to HTTPS) Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection. |
| 499 | (Client Closed Request) Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back. |
| 500 | (Internal Server Error) A generic error message, given when no more specific message is suitable. |
| 501 | (Not Implemented) The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually this implies future availability (eg. a new feature of a web-service API). |
| 502 | (Bad Gateway) The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
| 503 | (Service Unavailable) The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Sometimes, this can be permanent as well on test servers. |
| 504 | (Gateway Timeout) The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. |
| 505 | (HTTP Version Not Supported) The server does not support the HTTP protocol version used in the request. |
| 506 | (Variant Also Negotiates) Transparent content negotiation for the request results in a circular reference. |
| 507 | (Insufficient Storage) The server is unable to store the representation needed to complete the request. |
| 508 | (Loop Detected) The server detected an infinite loop while processing the request (sent in lieu of 208). |
| 509 | (Bandwidth Limit Exceeded) This status code, while used by many servers, is not specified in any RFCs. |
| 510 | (Not Extended) Further extensions to the request are required for the server to fulfil it. |
| 511 | (Network Authentication Required) The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g. "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot). |
| 598 | (Network read timeout error) This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy. |
| 599 | (Network connect timeout error) This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy. |