Error: Not Expected HTTP Response

Same issue.

Job "XXXX" has started, but not responded for 10 seconds. Please check information.

WordPress version	4.7
BackWPup version	3.3.4 Get pro.
PHP version	7.1.0 (64bit)
MySQL version	5.5.53-log
cURL version	7.29.0
cURL SSL version	NSS/3.19.1 Basic ECC
WP-Cron url:	https://qaq.cat/wp-cron.php
Server self connect:	Not expected HTTP response:
    Status-Code: 200
    Server: nginx
    Date: Mon, 12 Dec 2016 12:43:43 GMT
    Content-type: text/html; charset=UTF-8
    Vary: Accept-Encoding
    X-powered-by: PHP/7.1.0
    Content-encoding: gzip
Temp folder:	/.../wp-content/uploads/backwpup-20f49e-temp/
Log folder:	/.../wp-content/uploads/backwpup-20f49e-logs/
Server	nginx/1.10.2
Operating System	Linux
PHP SAPI	fpm-fcgi
Current PHP user	www
Maximum execution time	300 seconds
Alternative WP Cron	Off
Disabled WP Cron	Off
CHMOD Dir	0755
Server Time	12:43
Blog Time	20:43
Blog Timezone	Asia/Shanghai
Blog Time offset	8 hours
Blog language	zh-CN
MySQL Client encoding	utf8mb4
Blog charset	UTF-8
PHP Memory limit	256M
WP memory limit	40M
WP maximum memory limit	256M
Memory in use	4.00 MB
Disabled PHP Functions:	passthru, exec, system, chroot, chgrp, chown, shell_exec, proc_open, proc_get_status, popen, ini_alter, ini_restore, dl, openlog, syslog, readlink, symlink, popepassthru, stream_socket_server
Loaded PHP Extensions:	Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, cgi-fcgi, ctype, curl, date, dom, filter, ftp, gd, gettext, hash, iconv, intl, json, libxml, mbstring, mcrypt, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_sqlite, posix, session, shmop, soap, sockets, sqlite3, standard, sysvsem, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

• This reply was modified 8 years, 2 months ago by Balthild.
• This reply was modified 8 years, 2 months ago by Balthild.
• This reply was modified 8 years, 2 months ago by Balthild.

I got Status-Code: 200 too and it was because my PHP was set to 7.x. I put it back down to 5.5 (native) and now the back ups run fine for me.

Hi @all,

we have released a new BackWPup version and fixed php 7.1 incompatibilities. You can find more info about the new version 3.3.6 in our blog: https://backwpup.com/backwpup-version-3-3-6-now-available-php-7-1-compatibility/

Cheers
Christina

Greetings
I have just installed BackWPup and am getting same error, however I have installed v3.3.7, and the PHP is v 5.6.27. see below:

WordPress version 	4.7.4
BackWPup version 	3.3.7 Get pro. 
PHP version 		5.6.27 (64bit) 
MySQL version 		5.6.32-78.0-log 
cURL version 		7.45.0 
cURL SSL version 	OpenSSL/1.0.1e 
WP-Cron url: 		https://oliviaruth.com.au/wp-cron.php 
Server self connect: 	Not expected HTTP response:
			Status-Code: 200
			Content-length: 0
			Accept-ranges: bytes
			Date: Fri, 05 May 2017 03:38:54 GMT
			Age: 0
			Vary: User-Agent
			X-cache: uncached
			X-cache-hit: MISS
			X-backend: all_requests

I am confused. What do I need to change to get this plugin working properly?
New to WP but not new to tech (started in 1985).
BC

Hi @oliviaruthband, could you begin a new thread with your issue? It is probably not identical to the one in this thread, since this had to do with PHP 7.

To get you started though, I would try enabling WP_DEBUG and see if you get any errors reported in Server self connect.

Hi Brandon
I will start a new thread if that’s what is needed.

I enabled WP_DEBUG, ran the backup again, and there was no log file created in \wp-content, and I got the same http 200 error.
Enabling this actually broke the web site, which when accessed just displayed a heap of errors on the screen, so I changed it back.
This is insanely frustrating that this plugin does not work. Am I the only one? Site is a ‘managed wordpress hosting’ site on GoDaddy, if this helps.

absolute sheer frustration.
BC

Hi @oliviaruthband, I’m sorry for your frustration.

Generally when there are wp-cron errors, it is down to the host. You could ask your host why a script is having trouble accessing wp-cron.

Or, a fast workaround in such circumstances is to enable ALTERNATE_WP_CRON. You can do so by adding this in wp-config.php:

define( 'ALTERNATE_WP_CRON', true );

Thanks for your suggestions.
You know what? this is all too difficult.
I am going to uninstall your plugin and get one that works.

Thanks.

BC

Hi @oliviaruthband, I’m sorry to hear that. We’re happy to help, but sometimes there are conflicts with the host environment and such. We can work around those but it takes a bit of debugging.