Title: [Plugin: WordPress Backup to Dropbox] Two errors
Last modified: August 20, 2016

---

# [Plugin: WordPress Backup to Dropbox] Two errors

 *  [alFrame](https://wordpress.org/support/users/alframe/)
 * (@alframe)
 * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-backup-to-dropbox-two-errors/)
 * I am getting:
    Backup error on 2011-10-23 at 05:34:31: The backup process appears
   to have gone away. Resuming backup. Backup started on 2011-10-23 at 05:28:11
 * Seems no backup is ever completed. There should be a “Backup complete” message,
   right?
 * And I am getting: Warning: file_exists() [function.file-exists]: open_basedir
   restriction in effect. File(path/blog) is not within the allowed path(s): (path/
   blog/httpdocs:/tmp) in (path/blog/httpdocs/wp-content/plugins/wordpress-backup-
   to-dropbox/wp-backup-to-dropbox-file-tree.php on line 30
 * Paths not completed on purpose. PM me is you need the full path.
 * I browsed the web for over an hour and I talked to my provider. There’s something
   wrong with the plugin as it seems.
 * This is an awesome plugin and I would really really like to use it. I would even
   donate some if you have a donate button somewhere.
 * Please advise.
 * Many thanks
 * [http://wordpress.org/extend/plugins/wordpress-backup-to-dropbox/](http://wordpress.org/extend/plugins/wordpress-backup-to-dropbox/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [alFrame](https://wordpress.org/support/users/alframe/)
 * (@alframe)
 * [14 years, 6 months ago](https://wordpress.org/support/topic/plugin-wordpress-backup-to-dropbox-two-errors/#post-2362596)
 * Updated to 0.9.1 and still getting the same errors.
 * Backup still get’s lost and never succeeds.
 * Please, any help would be very appreciated.
 * Even if it’s just pointing out the thread with the solution in case I am missing
   something stupid here.
 * Thanks!
 *  Plugin Contributor [Michael De Wildt](https://wordpress.org/support/users/michaeldewildt/)
 * (@michaeldewildt)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-backup-to-dropbox-two-errors/#post-2362630)
 * Gday alFrame,
 * As a security measure some hosts set the open_base directory feature of PHP. 
   This means that the plugin can only read files that are in ‘path/blog/httpdocs’
   or ‘/tmp’ .
 * More info can be found here – [http://www.php.net/manual/en/ini.core.php#ini.open-basedir](http://www.php.net/manual/en/ini.core.php#ini.open-basedir)
 * I have found the issue and will work on a fix over the coming days.
 * Thanks for taking the time to let me know.
 * Cheers,
    Mikey
 *  Thread Starter [alFrame](https://wordpress.org/support/users/alframe/)
 * (@alframe)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-backup-to-dropbox-two-errors/#post-2362645)
 * Thanks for the info and thanks for working on it.
 * Really appreciated! Looking forward to be able to use it and I am reading
    up
   on the link you posted.
 * Sorry for my late reply.
 * Alex

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘[Plugin: WordPress Backup to Dropbox] Two errors’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-backup-to-dropbox_ffffff.
   svg)
 * [WordPress Backup to Dropbox](https://wordpress.org/plugins/wordpress-backup-to-dropbox/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-backup-to-dropbox/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-backup-to-dropbox/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [alFrame](https://wordpress.org/support/users/alframe/)
 * Last activity: [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-wordpress-backup-to-dropbox-two-errors/#post-2362645)
 * Status: not resolved