Thread Starter
hoorna
(@hoorna)
Does nobody recognize this problem and/or have a tip?
Hello @hoorna and @wongpk I would revert back to 2.1.17 and don’t upgrade until all the errors are resolved. Daniel is working on resolving all the errors reported so far with this huge upgrade.
I have the latest version on a test site but I am not upgrading on my live sites until I know that it works 100%.
Hope this helps you for now.
Kind regards
The odd thing is that, some of my sites works and some don’t. Some with 2.1.17 version too are sending error log instead of backup file too. Not sure if that is because WordPress upgrade or not.
Thread Starter
hoorna
(@hoorna)
@daniel,
Do you have a solution for this problem? I still (version 3.0.6) get the error which I reported a the beginning of this thread.
Meanwhile I found out that the problem only occurs when I try to start a job immediately. Jobs started by linux-cron (by calling “wget -q -O http://website-name/wp-con.php?doing_wp_cron >/dev/null 2>&1”) are running normaly.
Try to add this in the functions.php of you theme:
add_filter( 'https_local_ssl_verify', '__return_false' );
Thread Starter
hoorna
(@hoorna)
I will try it at the end of next week. On this moment it is impossible for me to test.
Can’t seem to get any version to work, after upgrading and then getting:
BackWPup The HTTP response test get a false http status (403)
It was an awesome plug I would have supported.
Hello @cindygobeyond, have you tried using the old version 2.1.17. This is the version that I am still using on all my websites. This version works without any issues for me.
Kind regards
