Facebook
Twitter
T
Triloxigen
Guest
What path do I have to give when I want to use a Perl script (in the CGI-bin).
I cannot find how to get working in the right way.
I cannot find how to get working in the right way.
-
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.
J
jamesyeeoc
Guest
Due to lack of more details (os, perl ver, etc) and lack of sleep, please see these search results:
https://forum.plesk.com/search.php?...d=898914&sortby=lastpost&sortorder=descending
https://forum.plesk.com/search.php?...d=898914&sortby=lastpost&sortorder=descending
T
Triloxigen
Guest
The OS is Fedora Core 1 
I already tried #!/usr/bin/perl (what I find in the posts before i created this topic) but that gives the 500 error.
I already tried #!/usr/bin/perl (what I find in the posts before i created this topic
) but that gives the 500 error.
J
jamesyeeoc
Guest
I didn't look through all the search results, but I don't want to *assume* anything, so please do not take any offense at the following questions (some of these were covered in different threads):
Did you check ownership and perms ?
Check the httpd.conf AddHandler ?
Ah damn, my mind just went blank on the other questions, and I'm too tired to read the other post results myself right now. Sorry.
Hopefully I'll remember this thread after I get some sleep. Otherwise, sorry I didn't have better suggestions.
Did you check ownership and perms ?
Check the httpd.conf AddHandler ?
Ah damn, my mind just went blank on the other questions, and I'm too tired to read the other post results myself right now. Sorry.
Hopefully I'll remember this thread after I get some sleep. Otherwise, sorry I didn't have better suggestions.
T
Triloxigen
Guest
I did not change any of those things, I assumed Plesk defines this stuff correctly when creating a account.
phoenixisp
Silver Pleskian
#!/usr/bin/perl is the correct path to perl. Make sure that you chmod the executable to 755.
T
Triloxigen
Guest
I did that, but still error 500 :|
G
Gorgon@
Guest
Login to the server using ssh and run:
whereis perl
This should give you the full path to the perl binary.
M
whereis perl
This should give you the full path to the perl binary.
M
phoenixisp
Silver Pleskian
What does your error log tell you?
T
Triloxigen
Guest
Already dit that..
I think the problem is something else...
I think the problem is something else...
T
Triloxigen
Guest
[Wed Jul 13 09:09:10 2005] [error] [client xx.xxx.xxx.xx] Premature end of script headers: sendorder.cgi
phoenixisp
Silver Pleskian
From my experience the error 'Premature end of script headers' usually arises when there is a permissions problem. Either that or bad paths detailed within the script itself.
T
Triloxigen
Guest
It is a standaard many used script.
I even tried 777 as permission.
I even tried 777 as permission.
T
tmonsen
Guest
If you run perl -c file.cgi, from the command line, do you get any compilation errors?
also check you definitly upload in ASCII and not binary, you will end up with horrible ^M characters on the end of every line (not viewable in all editors though)
If this is the case you can strip them easily using vi
vi filename
:%s/^v^m//g
where
^v = Ctrl +v
and
^m = Ctrl +m
You can also find that many windows based editors will add these illegal end of line characters, use a good editor like Scite where you can change/view the EOL if you need too.
If this is the case you can strip them easily using vi
vi filename
:%s/^v^m//g
where
^v = Ctrl +v
and
^m = Ctrl +m
You can also find that many windows based editors will add these illegal end of line characters, use a good editor like Scite where you can change/view the EOL if you need too.
