Problem running backup

I’m getting the same issue on one website I manage, yet it’s working normally on another:

Log from site the plugin’s broken on:

WordPress version: 6.1.1
BackWPup version: 4.0.0
PHP version: 7.4.30  (64bit)
MySQL version: 8.0.28-0ubuntu0.20.04.3
cURL version: 7.58.0
cURL SSL version: OpenSSL/1.1.1
WP-Cron url: https://www.mrtaxes.ca/wp-cron.php
Server self connect: Not expected HTTP response:
Status-Code: 200
Date: Wed, 04 Jan 2023 20:36:03 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-control: no-cache, must-revalidate, max-age=0
Set-cookie: wfwaf-authcookie-7d44acb36043ad91efca4f100f534c18=5%7Cadministrator%7Cmanage_options%2Cunfiltered_html
%2Cedit_others_posts%2Cupload_files%2Cpublish_posts%2Cedit_posts%2Cread
%7C18c5c018627431647a0ae8f7d191de5ce0b4b0796c401c175d4f977cd6a20849; expires=Thu, 05-Jan-2023 08:36:04 GMT; Max-Age=43200; path=/; secure; HttpOnly
Vary: IS_SUBREQ,Accept-Encoding,User-Agent
Upgrade: h2
Referrer-policy: no-referrer-when-downgrade
Content-length: 0
Content-type: text/html; charset=UTF-8

Document root: /home/mrtaxes/MrTaxes.ca/http
Temp folder: /home/mrtaxes/MrTaxes.ca/http/wp-content/uploads/backwpup-35918a-temp/
Log folder: /home/mrtaxes/MrTaxes.ca/http/wp-content/uploads/backwpup-35918a-logs/
Server: Apache
Operating System: Linux
PHP SAPI: cgi-fcgi
Current PHP user: mrtaxes
Maximum execution time: 600 seconds
BackWPup maximum script execution time: 30 seconds
Alternative WP Cron: Off
Disabled WP Cron: Off
CHMOD Dir: 493
Server Time: 20:36
Blog Time: 20:36
Blog Timezone: 
Blog Time offset: 0 hours
Blog language: en-US
MySQL Client encoding: utf8
PHP Memory limit: 256M
WP memory limit: 40M
WP maximum memory limit: 256M
Memory in use: 58.00 MB
Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, imagick, imap, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_sqlite, posix, pspell, session, soap, sockets, sodium, sqlite3, standard, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

Log from site the plugin’s working normally on: (funny thing is this site’s having server problems, so I’d expect this to be the site the plugin would fail on)

WordPress version: 6.1.1
BackWPup version: 4.0.0
PHP version: 8.0.25  (64bit)
MySQL version: 5.7.23-23
cURL version: 7.81.0
cURL SSL version: OpenSSL/1.1.1n
WP-Cron url: https://easycozy.ca/wp-cron.php
Server self connect: Not expected HTTP response:
Status-Code: 200
Date: Wed, 04 Jan 2023 20:40:34 GMT
Server: Apache
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-control: no-cache, must-revalidate, max-age=0
Strict-transport-security: max-age=31536000
Content-security-policy: upgrade-insecure-requests
X-content-type-options: nosniff
X-xss-protection: 1; mode=block
Expect-ct: max-age=7776000, enforce
Referrer-policy: Array
Vary: Accept-Encoding
Upgrade: h2,h2c
Host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==
X-frame-options: SAMEORIGIN
Content-length: 0
Content-type: text/html; charset=UTF-8

Document root: /home1/fivonex8/public_html/easycozy
Temp folder: /home1/fivonex8/public_html/easycozy/wp-content/uploads/backwpup-e72dd1-temp/
Log folder: /home1/fivonex8/public_html/easycozy/wp-content/uploads/backwpup-e72dd1-logs/
Server: Apache
Operating System: Linux
PHP SAPI: litespeed
Current PHP user: fivonex8
Maximum execution time: 600 seconds
BackWPup maximum script execution time: 30 seconds
Alternative WP Cron: Off
Disabled WP Cron: Off
CHMOD Dir: 493
Server Time: 20:40
Blog Time: 12:40
Blog Timezone: 
Blog Time offset: -8 hours
Blog language: en-US
MySQL Client encoding: utf8
PHP Memory limit: 512M
WP memory limit: 40M
WP maximum memory limit: 512M
Memory in use: 190.00 MB
Loaded PHP Extensions:: Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, SourceGuardian, Zend OPcache, bcmath, bz2, calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, json, libxml, litespeed, mbstring, mysqli, mysqlnd, odbc, openssl, pcntl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, readline, session, soap, sockets, sodium, sqlite3, standard, tidy, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib

Hello, I have the exact same problem with exact same behavior. backwpup is normally working on my site on PHP 7.4.x but when I update version PHP to 8.0.x, ther will start same problems.

Use alternate cron will no help, I see only blank screen too. Now, I tried this on two different sites, two different hostings.

I tested WP from about 5.8 to 6.1.1, your plugin with previous version and now the latest 4.0.0. Still the same.

I have tried it on a 3rd site, a database only backup ran no problem, the scheduled backups, both full site, and database only, ran OK, but when I just attempted to run a manual backup of the full site, the same no response error occurred. This is 3 different sites, on 3 different hosts, I’ve tested this on. Here’s the log for comparison:

WordPress version: 6.1.1
BackWPup version: 4.0.0
PHP version: 8.0.26  (64bit)
MySQL version: 10.3.37-MariaDB-1:10.3.37+maria~ubu2004
cURL version: 7.68.0
cURL SSL version: OpenSSL/1.1.1f
WP-Cron url: https://www.truevikingfinance.ca/wp-cron.php
Server self connect: Response Test O.K.
Document root: /customers/7/5/1/truevikingfinance.ca/httpd.www
Temp folder: /customers/7/5/1/truevikingfinance.ca/httpd.www/wp-content/uploads/backwpup-59792a-temp/
Log folder: /customers/7/5/1/truevikingfinance.ca/httpd.www/wp-content/uploads/backwpup-59792a-logs/
Server: Apache
Operating System: Linux
PHP SAPI: cgi-fcgi
Current PHP user: truevikingfinance.ca
Maximum execution time: 0 seconds
BackWPup maximum script execution time: 30 seconds
Alternative WP Cron: Off
Disabled WP Cron: Off
CHMOD Dir: 493
Server Time: 22:21
Blog Time: 17:21
Blog Timezone: America/Toronto
Blog Time offset: -5 hours
Blog language: en-CA
MySQL Client encoding: utf8mb4
PHP Memory limit: 536870912
WP memory limit: 40M
WP maximum memory limit: 536870912
Memory in use: 36.00 MB
Disabled PHP Functions:: disk_total_space,  diskfreespace,  exec,  system,  popen,  proc_open,  proc_nice,  shell_exec,  passthru,  dl
Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dba, dom, exif, fileinfo, filter, gd, gettext, hash, iconv, imagick, imap, intl, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, readline, session, soap, sodium, sqlite3, standard, sysvshm, tokenizer, xml, xmlreader, xmlwriter, xsl, zip, zlib

I changed my PHP version back to 7.4… Run Now doesn’t work still:

Unexpected HTTP response:Status-Code:?200
Server:?openresty
Date:?Fri, 06 Jan 2023 11:43:56 GMT
Content-length:?0
Strict-transport-security:?max-age=31536000; includeSubDomains

Also, before I made the PHP change, I tried scheduling a backup job for 30 minutes or so into the future. It doesn’t run at all.

hi there,

you can fix this by using another cron method.
modify wp-config.php ( you can find this file in your root directory ), and BEFORE the line:
/* That’s all, stop editing! Happy blogging. */
add this line:
define('ALTERNATE_WP_CRON' , true );

After that the job should works fine.

Hi,

Are you replying to me? duongcuong96?

If I try the alternate cron method, then the run now doesn’t work … but are you saying that the scheduled backup WILL work?

@robwilc – for scheduled events not firing on time or at all, I’ve found the plugin WP Crontrol helps fix this. They way WordPress Cron works is it only fires if the site receives an HTTP or HTTPS request – so if your site has long periods of no traffic, this can prevent Cron events from triggering. WP Crontrol fixes this by pinging the site when Cron events are scheduled so the scheduled tasks fire off on time.

@duongcuong96 – what exactly does that fix? Sheduled backups not running, or manual backups stalling and failing every time? That’s an issue that came with an update to this plugin back around mid January. So look to whatever you changed around that time and find the bug that broke manually running backups. This issue, for me, occurs across multiple sites I manage, affecting each of them slightly differently, some database backups work normally on, some they don’t, but in all cases, full backups always fail. A fix that fixes manual backups but breaks scheduled backups is no good, as I need those automatic backups to work, as I manage many sites as a pro web developer and don’t have the time to be running from site to site manually running daily backups, 7 days a week even through holidays.