• 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.

Holly **** I Think I Figured Out The Perl Problem

T

tecdady

Guest
this is unreal. i looked into the httpd.include file in the conf directory of one of my virtual domains. this is what was included for the execution of perl files in the httpd.include:

<Directory /home/httpd/vhosts/final9sports.com/httpdocs>
<IfModule mod_perl.c>
<Files ~ (\.pl$)>
SetHandler perl-script
PerlHandler ModPerl::Registry
Options ExecCGI
allow from all
PerlSendHeader On
</Files>


Anyone see a massive problem here?
<Directory /home/httpd/vhosts/final9sports.com/httpdocs>

eh... hmm. httpdocs? i changed the to cgi-bin. all scripts ran IMMEDIATELY. you have got to be kidding me. could this REALLY be the problem? this is on a psa 7.5.3 box. now im scared after reading that plesk overwrites these files, this will get changed back and everything will break again. can someone shed some light on this and let me know what ive found. and that if it is THE problem, where to fix a "master" conf file so that this wont get overwritten with the incorrect file location. and finally, CAN SWSOFT REALLY BE THIS F*CKING STUPID?
 
This is INCREDIBLE we have the same problem after rewriting a client's httpd.include in his conf directory. Well done swsoft, well done!
 
Back
Top