There schould be something more wiht backwpup in the header. Will be some headers removed on your installation ?
I’m sorry, I don’t know what that means. Can you please clarify what you’re asking?
I have not removed any headers.
My backups also work when reverting to the earlier BackWPup version.
I also got the same error? May I know, which version is working? I’ve been trying last 2 version prior to the recent one.
I have change a littel thing on checking in the last version. Now there will be a header x-backwpup... send and checked if that header comes back.
is a reverse proxy active?
Not sure about reverse proxy, but my stack is nginx + hhvm + mariadb + redis cache
It is installed using easyengine script.
Getting the same error and yes, the site is behind a reverse proxy.Reverting to the previous version of BackWPup restores functionality
I’m sorry, I don’t know what this means: “Now there will be a header x-backwpup… send and checked if that header comes back. is a reverse proxy active?”
I tried updating the plugin on a different WordPress website hosted with a different hosting company, and this is the error message I get:
Missing or not expected HTTP response headers:
date: Fri, 19 Feb 2016 17:14:09 GMT
server: Apache/2.2.31
allow: GET, POST, PUT
cache-control: no-store, no-cache, must-revalidate
expires: Sat, 26 Jul 1997 05:00:00 GMT
pragma: no-cache
set-cookie: (code deleted); path=/
connection: close
content-type: text/html; charset=UTF-8
(Note that there was a string of letters & numbers after “set cookie” above, which I deleted in case it is a security risk).
So now I’m seeing the same issue across three websites hosted with two different hosting companies. These are all standard WordPress installs.
Same problem here:
Fehlender order nicht erwarteter HTTP response header:
date: Sat, 20 Feb 2016 00:18:37 GMT
server: Apache
set-cookie: PHPSESSID=(removed by me); path=/
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
vary: Accept-Encoding
content-encoding: gzip
connection: close
content-type: text/html; charset=UTF-8
Same problem here:
Fehlender order nicht erwarteter HTTP response header:
date: Sat, 20 Feb 2016 17:36:22 GMT
server: Apache/2.2.15 (CentOS)
connection: close
content-type: text/html; charset=iso-8859-1
I reverted back to a previous version of backwpup (from backup) and the error went away. This certainly looks like a bug in the 3.2.4 update. If you have not updated yet, don’t.
Interesting – well I only loaded 3.2.4 for the first time on a clients site – used it many times elsewhere – replaced it with 3.2.3 but the problem has NOT gone away!
Same problem for all my sites and clients sites.
Problem occurred when I updated to the latest version.
