| 1 | ==Curl Exit Code Reference== | 
 
 
 
 
 | 2 | For use with ValExtLinks script (http://wiki.oni2.net/ValExtLinks). | 
 
 
 
 
 | 3 | Excerpted from the man page for 'curl'. | 
 
 
 
 
 | 4 |  | 
 
 
 
 
 | 5 | EXIT CODES | 
 
 
 
 
 | 6 | 1      Unsupported protocol. This build of curl has no support for this | 
 
 
 
 
 | 7 | protocol. | 
 
 
 
 
 | 8 |  | 
 
 
 
 
 | 9 | 2      Failed to initialize. | 
 
 
 
 
 | 10 |  | 
 
 
 
 
 | 11 | 3      URL malformed. The syntax was not correct. | 
 
 
 
 
 | 12 |  | 
 
 
 
 
 | 13 | 4      A  feature  or  option  that  was  needed to perform the desired | 
 
 
 
 
 | 14 | request was not enabled or was  explicitly  disabled  at  build- | 
 
 
 
 
 | 15 | time.  To  make  curl able to do this, you probably need another | 
 
 
 
 
 | 16 | build of libcurl! | 
 
 
 
 
 | 17 |  | 
 
 
 
 
 | 18 | 5      Couldn't resolve proxy.  The  given  proxy  host  could  not  be | 
 
 
 
 
 | 19 | resolved. | 
 
 
 
 
 | 20 |  | 
 
 
 
 
 | 21 | 6      Couldn't resolve host. The given remote host was not resolved. | 
 
 
 
 
 | 22 |  | 
 
 
 
 
 | 23 | 7      Failed to connect to host. | 
 
 
 
 
 | 24 |  | 
 
 
 
 
 | 25 | 8      Weird server reply. The server sent data curl couldn't parse. | 
 
 
 
 
 | 26 |  | 
 
 
 
 
 | 27 | 9      FTP  access  denied. The server denied login or denied access to | 
 
 
 
 
 | 28 | the particular resource or directory you wanted to  reach.  Most | 
 
 
 
 
 | 29 | often  you  tried to change to a directory that doesn't exist on | 
 
 
 
 
 | 30 | the server. | 
 
 
 
 
 | 31 |  | 
 
 
 
 
 | 32 | 10     FTP accept failed. While waiting for the server to connect  back | 
 
 
 
 
 | 33 | when  an active FTP session is used, an error code was sent over | 
 
 
 
 
 | 34 | the control connection or similar. | 
 
 
 
 
 | 35 |  | 
 
 
 
 
 | 36 | 11     FTP weird PASS reply. Curl couldn't parse the reply sent to  the | 
 
 
 
 
 | 37 | PASS request. | 
 
 
 
 
 | 38 |  | 
 
 
 
 
 | 39 | 12     During  an  active  FTP  session while waiting for the server to | 
 
 
 
 
 | 40 | connect back to curl, the timeout expired. | 
 
 
 
 
 | 41 |  | 
 
 
 
 
 | 42 | 13     FTP weird PASV reply, Curl couldn't parse the reply sent to  the | 
 
 
 
 
 | 43 | PASV request. | 
 
 
 
 
 | 44 |  | 
 
 
 
 
 | 45 | 14     FTP  weird  227  format.  Curl  couldn't  parse the 227-line the | 
 
 
 
 
 | 46 | server sent. | 
 
 
 
 
 | 47 |  | 
 
 
 
 
 | 48 | 15     FTP can't get host. Couldn't resolve the host IP we got  in  the | 
 
 
 
 
 | 49 | 227-line. | 
 
 
 
 
 | 50 |  | 
 
 
 
 
 | 51 | 16     HTTP/2 error. A problem was detected in the HTTP2 framing layer. | 
 
 
 
 
 | 52 | This is somewhat generic and can be one out of several problems, | 
 
 
 
 
 | 53 | see the error message for details. | 
 
 
 
 
 | 54 |  | 
 
 
 
 
 | 55 | 17     FTP  couldn't  set  binary.  Couldn't  change transfer method to | 
 
 
 
 
 | 56 | binary. | 
 
 
 
 
 | 57 |  | 
 
 
 
 
 | 58 | 18     Partial file. Only a part of the file was transferred. | 
 
 
 
 
 | 59 |  | 
 
 
 
 
 | 60 | 19     FTP couldn't download/access the given file, the RETR (or  simi- | 
 
 
 
 
 | 61 | lar) command failed. | 
 
 
 
 
 | 62 |  | 
 
 
 
 
 | 63 | 21     FTP quote error. A quote command returned error from the server. | 
 
 
 
 
 | 64 |  | 
 
 
 
 
 | 65 | 22     HTTP page not retrieved. The requested  url  was  not  found  or | 
 
 
 
 
 | 66 | returned  another  error  with  the HTTP error code being 400 or | 
 
 
 
 
 | 67 | above. This return code only appears if -f, --fail is used. | 
 
 
 
 
 | 68 |  | 
 
 
 
 
 | 69 | 23     Write error. Curl couldn't write data to a local  filesystem  or | 
 
 
 
 
 | 70 | similar. | 
 
 
 
 
 | 71 |  | 
 
 
 
 
 | 72 | 25     FTP  couldn't  STOR  file. The server denied the STOR operation, | 
 
 
 
 
 | 73 | used for FTP uploading. | 
 
 
 
 
 | 74 |  | 
 
 
 
 
 | 75 | 26     Read error. Various reading problems. | 
 
 
 
 
 | 76 |  | 
 
 
 
 
 | 77 | 27     Out of memory. A memory allocation request failed. | 
 
 
 
 
 | 78 |  | 
 
 
 
 
 | 79 | 28     Operation timeout. The specified  time-out  period  was  reached | 
 
 
 
 
 | 80 | according to the conditions. | 
 
 
 
 
 | 81 |  | 
 
 
 
 
 | 82 | 30     FTP  PORT  failed.  The PORT command failed. Not all FTP servers | 
 
 
 
 
 | 83 | support the PORT  command,  try  doing  a  transfer  using  PASV | 
 
 
 
 
 | 84 | instead! | 
 
 
 
 
 | 85 |  | 
 
 
 
 
 | 86 | 31     FTP  couldn't use REST. The REST command failed. This command is | 
 
 
 
 
 | 87 | used for resumed FTP transfers. | 
 
 
 
 
 | 88 |  | 
 
 
 
 
 | 89 | 33     HTTP range error. The range "command" didn't work. | 
 
 
 
 
 | 90 |  | 
 
 
 
 
 | 91 | 34     HTTP post error. Internal post-request generation error. | 
 
 
 
 
 | 92 |  | 
 
 
 
 
 | 93 | 35     SSL connect error. The SSL handshaking failed. | 
 
 
 
 
 | 94 |  | 
 
 
 
 
 | 95 | 36     Bad download resume. Couldn't continue an earlier aborted  down- | 
 
 
 
 
 | 96 | load. | 
 
 
 
 
 | 97 |  | 
 
 
 
 
 | 98 | 37     FILE couldn't read file. Failed to open the file. Permissions? | 
 
 
 
 
 | 99 |  | 
 
 
 
 
 | 100 | 38     LDAP cannot bind. LDAP bind operation failed. | 
 
 
 
 
 | 101 |  | 
 
 
 
 
 | 102 | 39     LDAP search failed. | 
 
 
 
 
 | 103 |  | 
 
 
 
 
 | 104 | 41     Function not found. A required LDAP function was not found. | 
 
 
 
 
 | 105 |  | 
 
 
 
 
 | 106 | 42     Aborted by callback. An application told curl to abort the oper- | 
 
 
 
 
 | 107 | ation. | 
 
 
 
 
 | 108 |  | 
 
 
 
 
 | 109 | 43     Internal error. A function was called with a bad parameter. | 
 
 
 
 
 | 110 |  | 
 
 
 
 
 | 111 | 45     Interface error. A specified outgoing  interface  could  not  be | 
 
 
 
 
 | 112 | used. | 
 
 
 
 
 | 113 |  | 
 
 
 
 
 | 114 | 47     Too many redirects. When following redirects, curl hit the maxi- | 
 
 
 
 
 | 115 | mum amount. | 
 
 
 
 
 | 116 |  | 
 
 
 
 
 | 117 | 48     Unknown option specified to libcurl.  This  indicates  that  you | 
 
 
 
 
 | 118 | passed  a weird option to curl that was passed on to libcurl and | 
 
 
 
 
 | 119 | rejected. Read up in the manual! | 
 
 
 
 
 | 120 |  | 
 
 
 
 
 | 121 | 49     Malformed telnet option. | 
 
 
 
 
 | 122 |  | 
 
 
 
 
 | 123 | 51     The peer's SSL certificate or SSH MD5 fingerprint was not OK. | 
 
 
 
 
 | 124 |  | 
 
 
 
 
 | 125 | 52     The server didn't reply anything, which here  is  considered  an | 
 
 
 
 
 | 126 | error. | 
 
 
 
 
 | 127 |  | 
 
 
 
 
 | 128 | 53     SSL crypto engine not found. | 
 
 
 
 
 | 129 |  | 
 
 
 
 
 | 130 | 54     Cannot set SSL crypto engine as default. | 
 
 
 
 
 | 131 |  | 
 
 
 
 
 | 132 | 55     Failed sending network data. | 
 
 
 
 
 | 133 |  | 
 
 
 
 
 | 134 | 56     Failure in receiving network data. | 
 
 
 
 
 | 135 |  | 
 
 
 
 
 | 136 | 58     Problem with the local certificate. | 
 
 
 
 
 | 137 |  | 
 
 
 
 
 | 138 | 59     Couldn't use specified SSL cipher. | 
 
 
 
 
 | 139 |  | 
 
 
 
 
 | 140 | 60     Peer  certificate cannot be authenticated with known CA certifi- | 
 
 
 
 
 | 141 | cates. | 
 
 
 
 
 | 142 |  | 
 
 
 
 
 | 143 | 61     Unrecognized transfer encoding. | 
 
 
 
 
 | 144 |  | 
 
 
 
 
 | 145 | 62     Invalid LDAP URL. | 
 
 
 
 
 | 146 |  | 
 
 
 
 
 | 147 | 63     Maximum file size exceeded. | 
 
 
 
 
 | 148 |  | 
 
 
 
 
 | 149 | 64     Requested FTP SSL level failed. | 
 
 
 
 
 | 150 |  | 
 
 
 
 
 | 151 | 65     Sending the data requires a rewind that failed. | 
 
 
 
 
 | 152 |  | 
 
 
 
 
 | 153 | 66     Failed to initialise SSL Engine. | 
 
 
 
 
 | 154 |  | 
 
 
 
 
 | 155 | 67     The user name, password, or similar was not  accepted  and  curl | 
 
 
 
 
 | 156 | failed to log in. | 
 
 
 
 
 | 157 |  | 
 
 
 
 
 | 158 | 68     File not found on TFTP server. | 
 
 
 
 
 | 159 |  | 
 
 
 
 
 | 160 | 69     Permission problem on TFTP server. | 
 
 
 
 
 | 161 |  | 
 
 
 
 
 | 162 | 70     Out of disk space on TFTP server. | 
 
 
 
 
 | 163 |  | 
 
 
 
 
 | 164 | 71     Illegal TFTP operation. | 
 
 
 
 
 | 165 |  | 
 
 
 
 
 | 166 | 72     Unknown TFTP transfer ID. | 
 
 
 
 
 | 167 |  | 
 
 
 
 
 | 168 | 73     File already exists (TFTP). | 
 
 
 
 
 | 169 |  | 
 
 
 
 
 | 170 | 74     No such user (TFTP). | 
 
 
 
 
 | 171 |  | 
 
 
 
 
 | 172 | 75     Character conversion failed. | 
 
 
 
 
 | 173 |  | 
 
 
 
 
 | 174 | 76     Character conversion functions required. | 
 
 
 
 
 | 175 |  | 
 
 
 
 
 | 176 | 77     Problem with reading the SSL CA cert (path? access rights?). | 
 
 
 
 
 | 177 |  | 
 
 
 
 
 | 178 | 78     The resource referenced in the URL does not exist. | 
 
 
 
 
 | 179 |  | 
 
 
 
 
 | 180 | 79     An unspecified error occurred during the SSH session. | 
 
 
 
 
 | 181 |  | 
 
 
 
 
 | 182 | 80     Failed to shut down the SSL connection. | 
 
 
 
 
 | 183 |  | 
 
 
 
 
 | 184 | 82     Could  not  load  CRL  file,  missing  or wrong format (added in | 
 
 
 
 
 | 185 | 7.19.0). | 
 
 
 
 
 | 186 |  | 
 
 
 
 
 | 187 | 83     Issuer check failed (added in 7.19.0). | 
 
 
 
 
 | 188 |  | 
 
 
 
 
 | 189 | 84     The FTP PRET command failed | 
 
 
 
 
 | 190 |  | 
 
 
 
 
 | 191 | 85     RTSP: mismatch of CSeq numbers | 
 
 
 
 
 | 192 |  | 
 
 
 
 
 | 193 | 86     RTSP: mismatch of Session Identifiers | 
 
 
 
 
 | 194 |  | 
 
 
 
 
 | 195 | 87     unable to parse FTP file list | 
 
 
 
 
 | 196 |  | 
 
 
 
 
 | 197 | 88     FTP chunk callback reported error | 
 
 
 
 
 | 198 |  | 
 
 
 
 
 | 199 | 89     No connection available, the session will be queued | 
 
 
 
 
 | 200 |  | 
 
 
 
 
 | 201 | 90     SSL public key does not matched pinned public key |