CustomBuild wp-cli open_basedir restriction in effect

[Wanabo]

System: AlmaLinux 9
Setup: DA, no modifications

I thought I mention this:

PHP Warning:  Phar::mapPhar(): open_basedir restriction in effect. File(/usr/local/bin/wp) is not within the allowed path(s): (/home/) in /usr/local/bin/wp on line 3
PHP Warning:  include(): open_basedir restriction in effect. File(wp-cli.phar) is not within the allowed path(s): (/home/) in /usr/local/bin/wp on line 4
PHP Warning:  include(): open_basedir restriction in effect. File(wp-cli.phar/php/boot-phar.php) is not within the allowed path(s): (/home/) in /usr/local/bin/wp on line 4
PHP Warning:  include(phar://wp-cli.phar/php/boot-phar.php): Failed to open stream: phar error: invalid url or non-existent phar "phar://wp-cli.phar/php/boot-phar.php" in /usr/local/bin/wp on line 4
PHP Warning:  include(): Failed opening 'phar://wp-cli.phar/php/boot-phar.php' for inclusion (include_path='.:/usr/local/php81/lib/php') in /usr/local/bin/wp on line 4
[1mUpdating WP-CLI(B[m
download_cached: using cached '/usr/local/directadmin/custombuild/cache/wp-cli-2.11.0.phar' file
WP-CLI 2.11.0 Installed.

 

[Wanabo]

Bump.

 

[Richard G]

It's a WP issue. In fact WP should obey open_basedir restrictions. However, you can change it by either removing the open_basedir restriction for the specific domain, or add the /usr/local/bin/wp path to the open basedir.

Check this, might be of help to you:

Post in thread 'Can't change open_basedir setting'

Oct 13, 2020

I'd personally aim for the per-account php-fpm.conf settings, rather than a .ini override that all other User's would "load" even if it's out of their path/host.

Admin Level » Custom Httpd Config » php-fpm

which should being you to a URL that might look like this, if it's for User "fred":

/admin/custom-httpd/fred/php-fpm/7.4/global_custom1

In the |CUSTOM1| php-fpm token, you'd add:

|?OPEN_BASEDIR_PATH=`OPEN_BASEDIR_PATH`:/mnt/mediastorage|

which should do the trick.

NOTE: I did find a segfault on CentOS 8 when testing this. It's now fixed...

• DirectAdmin Support

• 

 

[Richard G]

Just seen your other thread again too. I forgot about that one. If the open_basedir is also giving issues in the other thread, then probably something else is going on.
Because for sure it should not give issues with database and/or roundcube.

Maybe it's some customisation somewhere causing this. Pity you can't send in a ticket for this, you have Legacy license, right?

 

[Wanabo]

Not sure but I think the problems started after updating wp-cli in custom build.
I don't use wp and probably never will, but since it was an update I figured better safe than sorry.
Strange wp-cli is not optional but forced in your da installation.

 

[Richard G]

I don't know, doesn't seem to be a DA issue to me. I could be wrong. But we have several WP sites on all servers and until now we did not encounter this issue.