• Resolved jeffersonpowers

    (@jeffersonpowers)


    After updating to BackWPUp version 3.2.4, I get the following error message when I try to run a backup:

    Missing or not expected HTTP response headers:
    date: Tue, 16 Feb 2016 19:26:39 GMT
    server: Apache
    connection: close
    content-type: text/html; charset=iso-8859-1

    Rolling back to BackWPUp version 3.2.3 removes the problem, and I am able to run backups normally.

    https://www.ads-software.com/plugins/backwpup/

Viewing 15 replies - 46 through 60 (of 101 total)
  • Lindenism

    (@lindenism)

    People, after having the same problem, I also added:
    define( ‘ALTERNATE_WP_CRON’, true );

    This works, however I notice every 3rd or 4th URL has the cron link due to this rule:

    example: https://www.yourwebsite.com.au/?doing_wp_cron=231231231

    This rule ‘define( ‘ALTERNATE_WP_CRON’, true );’ is not a fix for this problem.

    Is the plugin author going to reply to this chain?

    reference: https://wordpress.stackexchange.com/questions/12777/why-is-doing-wp-cron-being-appended-to-my-urls

    bootupword

    (@bootupword)

    Backwpup was working prior to my webhost performing background resource changes that affected the folder location of my www files and my dns ip address for my websites. Normal procedure for my webhost to improve services but has obviously caused BackWPup to fail.

    Since that change, BackWPup has begin randomly failing with the errors I had mentioned in my earlier post, regardless of backwpup version used. (old or new) or any uninstalling/reinstalling/reconfiguring of this plugin etc.

    When I install BackWPup on a new site for the first time everything works as expected with this plugin. Lets hope the host doesn’t perform routine maintenance for a while yet.

    Plugin works “until” something absolute is no longer absolute.

    pako69

    (@pako69)

    define( 'ALTERNATE_WP_CRON', true ); and WPBackup 3.2.4 Works.

    But 48 posts on this feed and no anwsers from the author?!

    Where is he ?!

    yerom

    (@yerom)

    I made the “define( ‘ALTERNATE_WP_CRON’, true );” in wp_config.php and it’s works for me (backWPup 3.2.5).

    Hope this will be fix in the next plugin update

    Ramzii

    (@ramzii)

    A reply from the author would be nice, to say the least.

    syzygist

    (@syzygist)

    Automatic backups are now completing on the migrated account I mentioned in my last post (although I’m getting a warning, but I believe that is related to changing the server software versions).

    However, I am still getting this error on another host. I, too, wonder why neither www.ads-software.com nor the author are addressing what is obviously a bug that is affecting a very important function for many people (a whole lot of whom probably don’t even realize that their sites are not being backed up). I just went to the plugin description page and clicked the “broken” button (right sidebar, near the bottom). Maybe if a few more people do this the problem will get some attention.

    Daniel Hüsken

    (@danielhuesken)

    Hey Guys,

    it’s not easy to give support here, because there are many things that are not depends on the initial problem. Please open a own thread for other problems! Else i can’t support it.

    For those who uses a Reverse Proxy please try to set up Authentication with a WordPRess user in BackWPup > Settings > Tab: Network. Also you can try to remove this (https://github.com/inpsyde/backwpup/blob/master/inc/class-job.php#L551-L553) 3 Lines of code and test if it than work. Please give feedback if it works.

    Connect timeout is another problem that depends often on Server configuration. The problems can come from:
    – Hoster blocks loopback connections
    – Your site is to slow
    – other plugins
    – reverse proxy (cloudflare)
    – …

    The 3.2.5 was only a secuity release that dont fixes other bugs!

    Thread Starter jeffersonpowers

    (@jeffersonpowers)

    Hi Daniel —

    Removing the three lines of code from class-job.php fixes the problem.

    However, this is not a viable long-term solution, since that file will be replaced every time the plugin is updated, and It’s not going to be practical for users to have to re-edit the file every time the plugin updates.

    Is it possible to make whatever those lines of code are for, an option that can be turned off?

    Can you please give an estimate on how long it will take to fix this problem permanently? Thanks!

    EDIT: Please note that my post refers to the original problem reported at the top of this thread (I am the original poster). Thanks!

    bootupword

    (@bootupword)

    I removed the 3 lines, deactivated/re-activated plugin and received same error but displayed differently.

    Added 3 lines back and run job, and it worked. But today, its not working.

    If it is a performance issue with webhost then I’m not sure what I need to tweak to get backwpup server self connect function to not time out and report error The HTTP response test get an error “connect() timed out!”Missing or not expected HTTP response headers: .

    Perhaps next backwpup revision could add performance info in Settings that would inform us if this plugin will work or not based on user’s current webhost resources?

    Daniel Hüsken

    (@danielhuesken)

    @jeffersonpowers: Good to know. The line will be removed with the next update. We will release an update asap. In think in next week.

    @bootupword: When you open https://yourdomain.tld/wp-cron.php in a browser how long will it take ?

    bootupword

    (@bootupword)

    When I run the full http request for wp-cron.php it takes less than a second.

    Accessing Backwpup/Settings/Info takes 15+ seconds.

    Backwpup worked prior to my host changing a bunch of website ip addresses.

    I installed a new website domain with wordpress 4.4.2 and Backwpup 3.2.5 on same host and backup works fine.

    Unfortunately, deleting backwpup plugin and cleaning any backwpup references in mysql db has not resolved issue. I have also installed W3 Total Cache and it has improved response times but not fixed wp-cron connect time out.

    Call Stack results show this if its any help:

    WP_Http->head()
    wp-includes/class-http.php:448
    wp_remote_head()
    wp-includes/http.php:204
    BackWPup_Job::get_jobrun_url()
    wp-content/plugins/backwpup/inc/class-job.php:552
    BackWPup_Page_Settings::page()
    wp-content/plugins/backwpup/inc/class-page-settings.php:437
    do_action(‘backwpup_page_backwpupsettings’)
    wp-includes/plugin.php:525

    Daniel Hüsken

    (@danielhuesken)

    @bootupword; can the server correctly resolve the ip adress with the domain name?

    bootupword

    (@bootupword)

    I can ping domain name and receive new ip address reply.

    But, not access website via https://”ip address”. It’s a shared environment. Always has been and does not affect other sites in same environment running backwpup.

    I updated the salt keys, flushed caches, reactivated plugin but same error.

    bootupword

    (@bootupword)

    Is it having problem obtaining “BackWPup_Job::get_jobrun_url”?

    My URL resolves ok.

    Daniel Hüsken

    (@danielhuesken)

    “BackWPup_Job::get_jobrun_url” gets only the url and doing the request. The URL will use the site url and adds wp-cron.php to it. IT will use the similar way the wordpress cron uses.

    Did scheduled posts work ?

Viewing 15 replies - 46 through 60 (of 101 total)
  • The topic ‘Missing or not expected HTTP response headers’ is closed to new replies.