Viewing 4 replies - 16 through 19 (of 19 total)
  • The aktuel Version use the wpdb class for dumping if you have many posts it will load the complte posts teble in memory.

    I next Version i will go to native mysql funktions that dont has this problem.

    Phil Broughton

    (@prb22publicgmailcom)

    For info, I could not get wp-cron working and this turned out to be because the call it makes tries to spawn a local HTTP request from the host providing server which gets blocked (a loopback request if you like). Using alternate wp cron worked in this case to allow cron to work (because it makes the client, not the server call the wp-cron task), however the backup plugin, once fired needs to do a local HTTP request which takes me back to where I started… Basically if my host provider does not allow local HTTP get requests, then this plugin doesn’t work.
    I hope this is helpful, perhaps the plugin should document this under an FAQ ?

    I don’t know if this helps anyone, but I too am stuck on 0%.

    My server at the moment is in a strange state because it is being moved from one host to another. For a while, I have https://www.myhost_name.com working on the new server, but https://myhost_name.com is still pointing to the old server and is inaccessible.

    Daniel, when you say ‘make sure that the server can contact itself over http’ is it that it is using myhost_name.com and not the www version.

    Could it be that others here have not mapped the myhost_name.com version to their site? I know that its common for people to block this so that search engines are not confused.

    If this is the case then perhaps there should be a setting to specify the preferred url for the server?

    For my own case, I will find out soon because the DNS changes will take full effect in 24 hours and the server will be contactable with and without the www.

    ahoy all,

    i was having same 0% error on shared hosting on fresh install of plugin, checked Error Logs of Apache and saw lots of

    [Sat Feb 02 17:55:07 2013] [error] SoftException in Application.cpp:601: Directory "/home/XXXXX/wordpress/wp-content/plugins" is writeable by group

    errors while BackWPup was sitting at 0%. when i simply changed the /wordpress/wp-content/plugins to not be group writeable, the plugin started to backup, though currently it never reaches 100% on the “Working” page, but the backup does seem to be complete and correct.

    hope this helps.

    peace

Viewing 4 replies - 16 through 19 (of 19 total)
  • The topic ‘backup stay 0%’ is closed to new replies.