• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

How to disable php functions on per vhost level?

T

Traged1

Guest
How can one disable php functions on a per vhost level?

I have added to the vhost.conf file the following:

<Directory /home/httpd/vhosts/domain.com/httpdocs>
php_admin_value disable_functions fsockopen,pfsockopen,socket_create,socket_bind,socket_connect,socket_listen,socket_create,socket_strerror,fsocket
</Directory>

Then I used:

/usr/local/psa/admin/sbin/websrvmng -a -v

But it still allows the fsockopen(); in php for this vhost?

Is this possible to do or do I not have the correct syntax?

The reason I am doing this is to prevent customers from using thier own php sendmail programs and opening massive amounts of socks which leads to apache crashes with the [crit] too many files open error.

I can't disable the functions in php.ini because then webmail cannot send any email.

Alternatively, I would appreciate if anyone knows how I can designate a different php path for webmail?
 
disable_functions is only server-wide function. You can't enable or disable it for one vhost.
 
Then is there a way to change the location of the PHP which webmail uses?

It currently uses:
/usr/bin/php

Where I would like it to use:
/usr/local/psa/admin/bin/php
 
Hello.
Just curious,
Did you try turning it off in the hosting setup menu?

If I understand your question correctly, this should take care
of it.

Cheers.
 
Back
Top