Hi,
I have added the path to the custom php.ini in the correct section of my htaccess file using the custom code option in the plugin and I have created the new htaccess file and activated it so I can see the resulting file on the sever when I look via FTP.
I see..
# ADD A PHP HANDLER # If you are using a PHP Handler add your web hosts PHP Handler below # CUSTOM CODE TOP PHP/PHP.INI HANDLER/CACHE CODE - Your Custom htaccess code will be created here with AutoMagic SetEnv PHPRC /home/aditerum/public_html/php.ini
The reason I have a custom php.ini is to allow the use of fsockopen and escapeshellarg but I am also trying to configure Wanguard. And at the moment Wanguard continues to tell me that network functions are disabled….”Your web host or server administrator has disabled PHP’s fsockopen or gethostbynamel functions.” but my custom php.ini correctly enables fsockopen but something … somewhere … is stopping the custom php.ini from being seen and used so I assume it is something in the htaccess but I can’t find anything that sticks out like a sore thumb.
Prior to using BPS my Wanguard configuration was working, so my original (albeit feeble) htaccess file was allowing my custom php.ini to be seen/used. So there must be something I have missed or done incorrectly that is stopping this….but what?
Any pointers?
- This topic was modified 2 hours, 11 minutes ago by AITpro Admin.
- This topic was modified 2 hours, 10 minutes ago by AITpro Admin.