CURLE_SSL_ENGINE_NOTFOUND (53) The specified crypto engine wasn't found. Ask host to increase mysql memory. CURLE_SSL_CACERT (60) Peer certificate cannot be authenticated with known CA certificates. Return data: [Server response here] Commonly this is caused by the line added to the remote site's wp-config.php being in the wrong place. this contact form
Which current networking protocol would be the optimal choice for very small FTL bandwidth? CURLE_UPLOAD_FAILED (25) Failed starting the upload. The range "command" didn't work. 34 HTTP post error. This seems particularly true of connection errors. up down 4 david at liip dot ch ¶4 years ago you should look on http://php.net/manual/en/curl.constants.php for the error
In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to CURLE_LDAP_INVALID_URL (62) Invalid LDAP URL. The database already contains a WordPress installation with this prefix (27 tables). share|improve this answer edited Feb 5 '15 at 12:26 S.L.
For FTP, the server typically denied the STOR command. CURLE_FTP_WEIRD_PASV_REPLY (13) libcurl failed to get a sensible result back from the server as a response to either a PASV or a EPSV command. See logs above for more information. Curl Error Code 7 If the co-signer on my car loan dies, can the family take the car from me like they're threatening to? "You hear but you don't listen" or "You listen but you
Calling curl ends up with: curl: (18) transfer closed with 7512708716 bytes remaining to read Although this error occurs, the return code remains 200, so that my script "thinks" that everything CURLE_SSL_CIPHER (59) Couldn't use specified cipher. timoreimann commented Jul 18, 2014 @lazappa's advice to enforce HTTP 1.0 worked for me as well. http://stackoverflow.com/questions/1759956/curl-error-18-transfer-closed-with-outstanding-read-data-remaining ie: /www/wp-content/uploads/ Optionally manually create the directory and set permissions. 9003 BackupBuddy data file (backupbuddy_dat.php) missing or unreadable.
It means you should call curl_multi_perform again without doing select() or similar in between. Curl Response Code Php Check your permissions. (#directory#) Verify user permissions for this directory. CURLcode is one of the following: CURLE_OK (0) All fine. Unzipping may have taken too long and the PHP process halted.
CURLE_FTP_ACCEPT_FAILED (10) While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar. https://developer.salesforce.com/forums/?id=906F00000009AB1IAM Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively. Curl Http Code BackupBuddy must be able to create this directory to function properly. Curl Error 35 Barth 5,336113353 answered Feb 5 '15 at 8:51 Jorge Blanco 111 This does not provide an answer to the question.
Need an account? http://digitalezines.com/curl-error/curl-error-code-26.html CURLE_FTP_ACCEPT_TIMEOUT (12) During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired. CURLE_SSL_ENGINE_SETFAILED (54) Failed setting the selected SSL crypto engine as default! Permissions may be blocking backup file creation. Curl Error 60
Refer to the appropriate documentation. is not writable. CURLE_TFTP_UNKNOWNID (72) Unknown TFTP transfer ID. navigate here This should never happen if the server is sane.
Try disabling all other plugins to see if that fixes it. Curl Error 60 Ssl Certificate Problem This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Verify write permissions are properly configured for this file.
Verify you are using the correct active API key. CURLE_FTP_BAD_FILE_LIST (87) Unable to parse FTP file list (during FTP wildcard downloading). Error #3382.12:20:04: Failed function backup_zip_files. Curl Sslread() Return Error -9806 If libcurl fails to parse that line, this return code is passed back.
CURLE_AGAIN (81) Socket is not ready for send/recv wait till it's ready and try again. CURLE_FAILED_INIT (2) Very early initialization code failed. CURLE_FTP_BAD_DOWNLOAD_RESUME (36) Attempting FTP resume beyond file size. his comment is here BackupBuddy cannot always capture command line mysql error messages.
This error code is used for more than just FTP and is aliased as CURLE_WEIRD_SERVER_REPLY since 7.51.0. Curl couldn't parse the 227-line the server sent. 15 FTP can't get host. You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php. 9024 ERROR #9024: Connected to Amazon S3 For FTP, the server typically denied the STOR command.
Delete existing directory first if you wish to proceed or restore individual files.