Hi again Xavier12,
... some recommendations:
for www.conf:
;catch_workers_output = yes
to
catch_workers_output = yes
- Change ( please make sure, that the values meet YOUR OWN configuration... i.e. locate your php/perl/python - locations, because they vary on several linux distributions! )
Code:
;env[HOSTNAME] = $HOSTNAME
;env[PATH] = /usr/local/bin:/usr/bin:/bin
;env[TMP] = /tmp
;env[TMPDIR] = /tmp
;env[TEMP] = /tmp
to
Code:
env[HOSTNAME] = $HOSTNAME
env[PATH] = /bin:/usr/bin:/usr/local/bin:/usr/share/php:/usr/share/php5:/usr/share/perl:/usr/share/perl5:/usr/bin/python:/usr/bin/python3:/usr/share/psa-pear
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp
;php_admin_flag[log_errors] = on
to
php_admin_flag[log_errors] = on
- Add ( at the end and again: please make sure, that the values meet YOUR OWN configuration... i.e. locate your php/perl/python - locations, because they vary on several linux distributions! )
Code:
php_value[include_path] = ".:/bin:/usr/bin:/usr/local/bin:/usr/share/php:/usr/share/php5:/usr/share/perl:/usr/share/perl5:/usr/bin/python:/usr/bin/python3:/usr/share/psa-pear"
- After you finished editing the www.conf, consider renaming the file to "zzz_www.conf" ( or something similar ), to make sure, that Plesk or any other configurator will not override your own modifications for your global www.conf. Keep in mind, that if you add domains or modify some hosting - settings, Plesk might build another www.conf, because it thinks, that it might not be existent, when you renamed it.
Code:
php_value[max_execution_time] = 30
php_value[memory_limit] = 500M
php_value[open_basedir] = "/var/www/vhosts/example.com/:/tmp/"
to
( at the end and again: please make sure, that the values meet YOUR OWN configuration... i.e. locate your php/perl/python - locations, because they vary on several linux distributions! )
Code:
php_value[allow_url_fopen] = on
php_value[safe_mode] = off
php_value[memory_limit] = 512M
php_value[max_input_time] = 360
php_value[max_execution_time] = 360
php_value[post_max_size] = 256M
php_value[upload_max_filesize] = 192M
php_value[include_path] = ".:/bin:/usr/bin:/usr/local/bin:/usr/share/php:/usr/share/php5:/usr/share/perl:/usr/share/perl5:/usr/bin/python:/usr/bin/python3:/usr/share/psa-pear"
php_value[open_basedir] = "/var/www/vhosts/example.com/:/tmp/:/bin:/usr/bin:/usr/local/bin:/usr/share/php:/usr/share/php5:/usr/share/perl:/usr/share/perl5:/usr/bin/python:/usr/bin/python3:/usr/share/psa-pear"
php_admin_flag[engine] = on
- After you finished editing the example.com.conf, consider renaming the file to "zzz_example.com.conf" ( or something similar ), to make sure, that Plesk or any other configurator will not override your own modifications for your domain-specific example.com.conf. Keep in mind, that if you add domains or modify some hosting - settings, Plesk might build another example.com.conf, because it thinks, that it might not be existent, when you renamed it.
You might notice, that I recommend higher/other PHP values, which you should as well change in your custom PHP - settings either over the webhosting - settings on the Plesk Control Panel, or directly at:
/var/www/vhosts/system/example.com/etc/php.ini
Be aware that if you change it over the Plesk Control Panel, Plesk will override any existent example.com.conf, which you just edited manually ( therefore the suggestion to rename this file ^^ ).
I noticed, that your server is still vulnerable, because of the poodle vulnerability. Please consider reading:
Your standard configuration for the
fcgid.conf could be optimized, please see the following KB - article (
Domain shows 500 internal server error: mod_fcgid: read data timeout ( KB - article 121 251 ) ) , even if the KB - article doesn't describe your specific issue. Consider setting another
fcgid.conf - configuration, as suggested by Parallels, which is a bit more specific and more detailled:
Code:
# This is the Apache server configuration file for providing FastCGI support
# via mod_fcgid
#
# Documentation is available at http://fastcgi.coremail.cn/doc.htm
<IfModule mod_fcgid.c>
<IfModule !mod_fastcgi.c>
AddHandler fcgid-script fcg fcgi fpl
</IfModule>
FcgidIPCDir /var/lib/apache2/fcgid/sock
FcgidProcessTableFile /var/lib/apache2/fcgid/shm
FcgidInitialEnv RAILS_ENV production
FcgidIdleTimeout 3600
FcgidBusyTimeout 1800
FcgidProcessLifeTime 0
FcgidMaxProcesses 150
FcgidMaxRequestsPerProcess 500
FcgidMaxProcessesPerClass 20
FcgidMinProcessesPerClass 0
FcgidConnectTimeout 60
FcgidIOTimeout 1800
MaxRequestLen 2147483648
FcgidMaxRequestLen 2147483648
FcgidIdleScanInterval 480
FcgidZombieScanInterval 12
FcgidErrorScanInterval 12
FcgidSpawnScoreUpLimit 10
FcgidSpawnScore 1
FcgidTerminationScore 2
</IfModule>
... but please still change the custom "
domainVirtualHost.php", as described in the mentioned article, but with the difference to modify the custom template like this:
Code:
FcgidMaxRequestLen 2147483648
FcgidIOTimeout 1800
Another issue/problem/failure/cause might be, that you missed to recreate the templates after some modifications. This can be resolved with the command:
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
or
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain YOURDOMAIN.COM
If you still experience further issues/problems, even if you restarted apache, nginx and php5-fpm with the commands:
service apache2 restart && service nginx restart && service php5-fpm restart
( please keep in mind, that on some linux systems the command to restart apache is "service httpd restart" ), you could try to use the bootstrapper command, which solves quite a lot ot issues:
/usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair
and make sure, that your Plesk installation is up-to-date:
/usr/local/psa/admin/bin/autoinstaller --select-product-id plesk --select-release-current --reinstall-patch --install-component base
Don't hesitate to include again error - logs and configuration files as done before... but shorten the logs to the actual date please, so that investigations are faster, if you experience further issues. Please include then as well
all config files from "
/var/www/vhosts/system/example.com/conf"
Facebook
Twitter