1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

wierd problem with cgi-bin

Discussion in 'Plesk for Linux - 8.x and Older' started by ZopfWare, Mar 16, 2005.

  1. ZopfWare

    ZopfWare Regular Pleskian

    May 30, 2004
    Likes Received:
    I just installed nagios for doing server monitoring and all of a sudden my cgi-bin directories were giving me fits.

    I had to install the following to get the nagios app to work:


    the above were required to resolve dependencies.

    Now when I try to run something from my cgi-bin I get the following error:

    /home/httpd/vhosts/prescriptionrx.net/cgi-bin/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.prescriptionrx.net/login.html

    However after a little research I found out that there may be a bug in php when it is used with the Crypt module???

    I don't know what has happened.

    I found that if I gave my cgi-bin directory the following perms all is fine.

    cgi-bin rwx r-x --x
    it works again.

    I don't understand why the default plesk perms of rwx for owner and r-x for group no longer work.

    Why did I have to give e(x)ecute permissions to other to get my cgi scripts to run again?
    Would really love to know the answer to this.
  2. Who-m3

    Who-m3 Guest

    You're running into this problem because the cgi-bin directory itself is set as a scriptalias. This means that all files under the directory are automatically parsed as though they are scripts. The best place for the .htaccess file you're trying to work with would be to put it in your private/ directory. This will ensure, under all circumstances, no users are able to obtain your htaccess file (increasing your security a bit).

    A simple re-write to the script configurations that utilize that specific .htaccess file should allow you to correctly operate your script without running into this error under normal circumstances (i.e. standard permissions).