• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

CGI/Perl issue after upgrade

R

redpaint

Guest
Hi Folks,

I've looked through the KB and the forums and at a loss to fix a cgi/perl problem after upgrade to 8.3.

I think it may be a permissions error but I'm not sure (novice).

I've looked at http://kb.swsoft.com/en/762 and my server kicks back:

plesk# ls -la /usr/local/sbin/suexec
-rwxr-xr-x 1 root wheel 18508 Jan 11 11:15 /usr/local/sbin/suexec

Could this be the problem?

suexec_log has the following:

[2008-01-10 10:03:18]: uid: (10009/####) gid: (2524/2524) cmd: nq000001.pl

Thanks in advance
 
Hi,

First of all, replace default "suexec" with the one shipped with Plesk software:
# cp $PRODUCT_ROOT_D/suexec/psa-suexec /usr/sbin/suexec

CGI script should locate in /cgi-bin/ and it should have:
owner: FTP user for current domain
group: 'psacln'

Also, it should have execution permissions.
 
Hi Satoriya,

I had already tried replacing suexec, what I didn't realise was that I had two instances of apache, the one running was installed in a non standard location and when I tried to overwrite suexec it appeared to work but had no effect as it was overwriting files on the old apache directory.

Thanks for your reply though, you were absolutely correct that suexec was the problem.
 
Back
Top