I am not much of a developer and when I had a problem with Actinic I had to start fault finding from the ground up.

Actinic puts a number of Perl and CGI scripts in the cgi-bin dir. To rule out Actinic the first thing I tried was a simple Perl test script:

#!/usr/bin/perl
print "Content-type: text/plain\n\n";
print "testing...\n";

Now try to access the page in your browser again. If it works (you see "testing..." as its output) then you know that your server is at least configured properly for running Perl CGI scripts and the issue must be with Actinic. If it doesn't work, then that may mean the problem is in the server configuration, rather than with your CGI script.

If you have access to the log files on your server you can check suexec_log normally found in /var/log/httpd/

If you see something like:

directory is writable by others: (/var/www/vhosts/thesupportsystem.com/cgi-bin)

Then this is a simple fix all you need to do is 755 the cgi-bin directory

chmod 755 /var/www/vhosts/thesupportsystem.com/cgi-bin

or

file has no execute permission: (/var/www/vhosts/thesupportsystem.com/cgi-bin/test.pl

Then all you need to do is 755 the file

chmod 755 var/www/vhosts/thesupportsystem.com/cgi-bin/test.pl

Related Posts

No related posts.