open_basedir: backup dir is not within the allowed path

Hi @,
Could you please contact your hosting provider and ask them something like that:

“Hi, I have an error on my WordPress site, it shows:
open_basedir: backup dir is not within the allowed path
”
This plugin has nothing to do with this problem.
Hope that help, if it’s not, please comment below and we will go further ??

Hi,
why should it depend on hosting provider or OS, when I have a virtual root server and have changed nothing. This is the relevant line in my vhost config which for one year (!!!) on that server:

php_admin_value open_basedir /var/www/budokan/:/NFS/backup/COWTUX/Websites/WP-Backups/Budokan/

Take a look at the error message and find the error …

FEHLER: Ausnahme eingefangen in RuntimeException: SplFileInfo::isWritable(): open_basedir restriction in effect. 
              File(/NFS/backup/COWTUX/Websites/WP-Backups/Budokan/..) is not within the allowed path(s): 
(/var/www/budokan/:/NFS/backup/COWTUX/Websites/WP-Backups/Budokan/)

The problem are the two dots at the end of the path used by plugin (since last version?).
Path “…/WP-Backups/Budokan/..” => WP-Backups/
and not the sub-directory it should be (like before), because this plugin for this domain should only access sub-directory for this domain and not directory above.

As I told in my first post this error happens since plugin uses prefix backwpup_ebc97501_ for archive names and therefore this was introduced this month for me – with an update of the plugin which changed behavior for archive names!

After changing my vhost config to this everything is working without error, but this ist not what I expect:
php_admin_value open_basedir /var/www/budokan/:/NFS/backup/COWTUX/Websites/WP-Backups/

Check file handling in plugin, please. I think there was changed something.

=========================================
Bakup files on my server:

ROOT @ cowtux => /NFS/backup/COWTUX/Websites/WP-Backups/Budokan
# > ls -ldhtr *
-rw-r--r-- 1 www-data www-data   1 2012-08-23 11:20 index.php
-rw-r--r-- 1 www-data www-data 41M 2017-04-24 04:01 Budokan_backwpup_2017-04-24_03-00-48.zip
-rw-r--r-- 1 www-data www-data 41M 2017-05-01 04:21 Budokan_backwpup_2017-05-01_03-20-50.zip
-rw-r--r-- 1 www-data www-data 42M 2017-05-08 04:05 Budokan_backwpup_2017-05-08_03-05-08.zip
-rw-r--r-- 1 www-data www-data 42M 2017-05-15 04:02 Budokan_backwpup_2017-05-15_03-01-51.zip
-rw-r--r-- 1 www-data www-data 44M 2017-05-22 04:04 Budokan_backwpup_2017-05-22_03-04-21.zip
-rw-r--r-- 1 www-data www-data 44M 2017-05-29 04:01 Budokan_backwpup_2017-05-29_03-01-09.zip
-rw-r--r-- 1 www-data www-data 44M 2017-06-05 04:01 Budokan_backwpup_2017-06-05_03-00-47.zip
-rw-r--r-- 1 www-data www-data 44M 2017-06-12 04:02 Budokan_backwpup_2017-06-12_03-01-29.zip
-rw-r--r-- 1 www-data www-data 44M 2017-06-19 04:01 Budokan_backwpup_2017-06-19_03-00-13.zip
-rw-r--r-- 1 www-data www-data 44M 2017-06-26 04:01 Budokan_backwpup_2017-06-26_03-00-24.zip
-rw-r--r-- 1 www-data www-data 44M 2017-07-03 04:00 Budokan_backwpup_2017-07-03_03-00-15.zip
-rw-r--r-- 1 www-data www-data 44M 2017-07-10 04:01 Budokan_backwpup_2017-07-10_03-01-13.zip
-rw-r--r-- 1 www-data www-data 44M 2017-07-17 04:01 Budokan_backwpup_2017-07-17_03-01-10.zip
-rw-r--r-- 1 www-data www-data 44M 2017-07-24 04:01 Budokan_backwpup_2017-07-24_03-00-33.zip
-rw-r--r-- 1 www-data www-data 44M 2017-07-31 04:01 Budokan_backwpup_2017-07-31_03-00-11.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-07 04:00 backwpup_ebc97501_Budokan_backwpup_2017-08-07_03-00-16.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-14 04:01 backwpup_ebc97501_Budokan_backwpup_2017-08-14_03-01-08.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-16 18:31 backwpup_ebc97501_Budokan_backwpup_2017-08-16_17-31-18.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-16 18:40 backwpup_ebc97501_Budokan_backwpup_2017-08-16_17-39-48.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-16 18:43 backwpup_ebc97501_Budokan_backwpup_2017-08-16_17-42-59.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-16 18:56 backwpup_ebc97501_Budokan_backwpup_2017-08-16_17-56-33.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-17 17:17 backwpup_ebc97501_Budokan_backwpup_2017-08-17_16-16-57.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-17 17:18 backwpup_ebc97501_Budokan_backwpup_2017-08-17_16-17-59.zip
-rw-r--r-- 1 www-data www-data 44M 2017-08-17 17:21 backwpup_ebc97501_Budokan_backwpup_2017-08-17_16-21-36.zip

• This reply was modified 7 years, 3 months ago by tronic69.

Hi @tronic69,

I think this might be a bug in BackWPup.

Try changing line 247 of inc/class-destination-folder.php.

Currently it is this:

if ( $file->isWritable() && ! $file->isDir() && ! $file->isLink() ) {

Please change it to this:

if ( ! $file->isDot() && $file->isWritable() && ! $file->isDir() && ! $file->isLink() ) {

Please let us know if that works. If so it’ll be fixed in the next version.

Hi Brandon,

in my plugin it was line 200. ??

I changed the line and put back my vhost config to old state and now it worked without any trouble.
So, you can put this fix into next version.

Thanks for quick support and have a nice weekend!

Best regards,
Tom

Thanks @tronic69, I’m so happy it worked for you. ?? Let us know if you need anything else in the future.

Hello,

it seems this bug was reintroduced in Version 3.4.4.

Content of line 200 in /inc/class-destination-folder.php:
if ( $file->isWritable() && ! $file->isDir() && ! $file->isLink() ) {

After changing this line to following it worked again:
if ( ! $file->isDot() && $file->isWritable() && ! $file->isDir() && ! $file->isLink() ) {

I think you should check your RCS/repository. Maybe someone checked out an old code. So, please fix it in next version.

Thanks in advance,
Tom

I have just figured out that backups on a client site haven’t since October 2017. Same problem like described here. I changed /inc/class-destination-folder.php with no luck. This is the only installation where this error occurs. I have no idea what’s going on.

Every day the marmot greets … updated to version 3.5.1 (in WordPress 4.9.6) and *bang* the error is back.

It seems like it’s another root cause this time, because I checked file class-destination-folder.php and my bugfix is still there.

Any idea why?