Announcement

Collapse
No announcement yet.

CGI folder (403) Access Forbidden Error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    CGI folder (403) Access Forbidden Error

    Created "cgi" folder, in web root folder, ("cgi-bin" not available)
    Followed instructions on Uploading Store to Web site.
    Directories.. screen, correctly identified CGI-BIN Directory as "/cgi/".
    After the "Trying CGI-BIN guesses" procedure, the CGI-BIN URL screen displays the cgi location as "http://www.nisis.com/cgi-bin/".
    Corrected this to "http://www.nisis.com/cgi/" and the following ConnectionWizard error message is displayed :-

    The specified CGI-BIN URL or possibly the path to the CGI-BIN is not correct. Check the CGI-BIN URL and try again. If the CGI-BIN is correct, return to the first page of the wizard and turn on the button to confirm each setting. Then progress through the dialogs once again and verify that the path to the cgi-bin is also correct. The web server returned (403) Access Forbidden.

    Web server is running Windows NT.

    Would gratefully receive any suggestions on how to correct this problem, please.

    #2
    If you are using Windows NT you probably need your web host to set up a virtual directory called 'cgi' within the IIS setup which maps to your 'cgi' folder.

    Then, you need to set the permissions correctly, these are detailed below (and taken from the Advanced User Guide):

    NT Server will require 'read, write, execute, delete' permissions in the 'cgi-bin' and 'acatalog' directories for the FTP account user ID. The acatalog directory also requires the 'IUSER_<servername> internet guest' account to have access with 'read, write, execute, delete' permissions.

    Actinic also requires NTFS file permissions for the CGI-BIN and acatalog directories within IIS of 'read and execute' for 'cgi-bin' and 'read, write, execute' for the 'acatalog' directory.

    Comment


      #3
      Thank you so much for your prompt and acurate diagnosis.
      I passed on your suggestions to our ISP, who carried them out, and all is now working perfectly.
      Again, many thanks.
      Stephen Marmoy

      Comment

      Working...
      X