YES YOU'R right!
i didn't know that the /cgi-bin dir was an alias and so "linked" direct into the web. when i now point to www.muv.local/cgi-bin/hello_world.pl i am a little bit better. til now i got a 404 file not found. from now on i get a 500 internal server error. i think this is a little bit better. the next thing to do is to check the log-files. i'l do this tomorrow!

What I found is that you need to change the permissions to 777 and accept changes. Then change the permissions back to 655 and then it should work.

Click to expand...

THAT'S IT i looked into the error log and found, that suexec stops execution if the file is writeable by others than the owner!!!!

chmod to 777 is TO MUCH RIGHTS! All can write the script an suexec generates a error 500!!!

chmod 755 is exactly what suexec needs an the script runs!!!

@til
maybe we should add a cronjob which runs every 30 minutes and changes the rights, because if a user uploads a script and didn't know this he sets the wrong parameter and a 500 error is generated (and the user thinks the provider makes something wrong).

maybe we should add a cronjob which runs every 30 minutes and changes the rights, because if a user uploads a script and didn't know this he sets the wrong parameter and a 500 error is generated (and the user thinks the provider makes something wrong).

Click to expand...

I don't think it's a good idea to incapacitate users with a cron job. If we did this, we will have dozens of posts asking why ISPConfig changes the permissions of scripts without asking...

I don't think it's a good idea to incapacitate users with a cron job. If we did this, we will have dozens of posts asking why ISPConfig changes the permissions of scripts without asking...

Click to expand...

you are right. This is in deep a problem. but the other side is: how many users didn't know anything about rights. they upload a file and wonder why the script returns a 500 error.

maybe a hint at the 500-page itself is a good idea?

by the way: suphp has the same "problem". ISPConfig by default sets the document-root of the web to "group writeable" and your howto for suphp at this site sets the config of suphp to "create error if the dir is group writeable". This means, suphp will not work if u install suphp like your howto says. only after changing

Code:

allow_directory_group_writeable=true

instead of false, suphp works fine. If you don't change the line you get a 500

I'm also getting the Internal Server (500) Error when running the hello_world.pl when Suexec is Enabled. No errors when Suexec is Disabled.
I've checked the Log file and it shows this output:"Premature end of script headers: hello_world.pl"

Does anyone know what might be causing the problem or how to fix this?

I'm also getting the Internal Server (500) Error when running the hello_world.pl when Suexec is Enabled. No errors when Suexec is Disabled.
I've checked the Log file and it shows this output:"Premature end of script headers: hello_world.pl"

Does anyone know what might be causing the problem or how to fix this?

Thanks!

Click to expand...

Is the file owned by the web administrator user and group and which permissions has the file?