This is a good instruction i found for pemissions<\/p>\n
Directory permissions and ownership are important too.<\/p>\n
The \/var\/log\/httpd\/suexec_log\u00a0 is the place to look when regular error_log doesn\u2019t show anything\u2026<\/p>\n
\u00a0<\/p>\n
Firstly, make sure you upload the script into the cgi-bin in ASCII mode. This is a problem more oftern then you can imagine. chmod 755 the script. Check permissions are USERID:psacln (the directory should be USERID:psaserv). Of course check that the site has CGI support ticked. You can also verify the syntax of the script by running \u201cperl -c SCRIPTNAME.CGI\u201d and it should report syntax ok.
\nIf you\u2019re still having problems then check the logs. Check \/home\/httpd\/vhosts\/DOMAIN\/statistics\/logs\/error_log (some installs my use \/var\/www\/ as opposed to the plesk standard \/home\/httpd\/vhosts) and look for errors. This log file will usually show the error message on the screen. You may also need to check \/var\/log\/httpd\/error_log. If you still don\u2019t see the problem then check \/var\/log\/httpd\/suexec.log for any<\/p>\n
Finally, check the correct suexec version is being used. do an \u201cls -la \/usr\/sbin\/suexec\u201d and compare that to \/usr\/local\/psa\/suexec\/psa-suexec. If they are different then make a backup copy of \/usr\/sbin\/suexec to something like \/usr\/sbin\/suexec.orig. then either copy or make a symlink of \/usr\/local\/psa\/suexec\/psa-suexec into the \/usr\/sbin directory.<\/p>\n
Hopefully this has been helpful.<\/p>\n","protected":false},"excerpt":{"rendered":"
This is a good instruction i found for pemissions Directory permissions and ownership are important too. The \/var\/log\/httpd\/suexec_log\u00a0 is the place to look when regular error_log doesn\u2019t show anything\u2026 \u00a0 Firstly, make sure you upload the script into the cgi-bin … Continue reading