Test Files

[mlz]

Originally Posted by vogelor

www.muv.local/hello_word.pl (that means, YOU can't access the file from your pc)

isn't that ok?

Er, for the Pl, I believe it MUST be in cgi-bin so the URL should be: www.muv.local/cgi-bin/hello_world.pl in your example.

[vogelor]

Originally Posted by mlz

Er, for the Pl, I believe it MUST be in cgi-bin so the URL should be: www.muv.local/cgi-bin/hello_world.pl in your example.

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!

[falko]

Originally Posted by vogelor

from now on i get a 500 internal server error. i think this is a little bit better.

Make sure hello_world.pl is executable. Also switch off SuExec for now (until you get it working).

[vogelor]

Originally Posted by mphayesuk

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.

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

[falko]

Originally Posted by vogelor

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

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

[vogelor]

Originally Posted by falko

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

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

allow_directory_group_writeable=true

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

[falko]

Originally Posted by vogelor

This means, suphp will not work if u install suphp like your howto says.

But I didn't write the tutorial for use with ISPConfig. Not all tutorials on this web site are related to ISPConfig.

[vogelor]

Originally Posted by falko

But I didn't write the tutorial for use with ISPConfig. Not all tutorials on this web site are related to ISPConfig.

i know. what i exact mean was "the howto at your site".

And this was not meant as a critic, this was meant as a "good to know" or "maybe one should change the howto and add a comment for ISPConfig"

[falko]

Originally Posted by vogelor

And this was not meant as a critic

I know.

[Daisy]

yep. Yucky zip. File is corrupted.