• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved PHP Warning: parse_ini_file(): open_basedir restriction in effect

LionKing

Regular Pleskian
Server operating system version
Linux Ubunto 22.04
Plesk version and microupdate number
Plesk Obsidian Web Host Edition Version 18.0.58 Update #2
I'm seeing this issue on our Plesk server:


PHP Warning: parse_ini_file(): open_basedir restriction in effect. File(/opt/plesk/php/8.1/etc/php.ini) is not within the allowed path(s): (/var/www/vhosts/somdomain.com/:/tmp/) in /var/www/vhosts/some-domain.com/public_html/wp-content/plugins/booknetic-payment-square/vendor/apimatic/jsonmapper/src/JsonMapper.php on line 129

I see that there is a reference to WP plugins so I'm not certain if the plugin is the issue or that the system doesn't get full access to the php.ini file in Linux?

Any thoughts on how to solve this?

Kind regards
 
You could add the path to the PHP configuration directory to the "open_basedir" setting in your PHP settings. However, I believe that this will make your server very unsafe, because then scripts will be able to access all the files stored there and maybe even change them.
 
You could add the path to the PHP configuration directory to the "open_basedir" setting in your PHP settings. However, I believe that this will make your server very unsafe

Yes, not worth it. I guess Ishould just ignore it as it is probably the plugin that is making a code request to somewhere it shouldn't.
 
I been looking into this again and one thing that stands out as a sore thumb is:
PHP Warning: parse_ini_file(): open_basedir restriction in effect. File(/opt/plesk/php/8.2/etc/php.ini)
E.g it is the PHP ini file for version 82. that is being blocked.
In my little world PHP should not be blocked from working on the server, right?
 
Code:
/var/www/vhosts/some-domain.com/public_html/wp-content/plugins/booknetic-payment-square/vendor/apimatic/jsonmapper/src/JsonMapper.php
should not be accessing
Code:
/opt/plesk/php/8.2/etc/php.ini
 
Back
Top