Announcement

Collapse
No announcement yet.

Actinic Business V.6 - CGI-BIN error 404

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Actinic Business V.6 - CGI-BIN error 404

    Hello,

    My name is Martin from Cnx Solutions. I'm posting on behalf of one of our clients "Sea Chest"

    We have migrated our web services over to a brand new sever and unfortunately the Actinic software they are using is a fair few years old. We've had issues connecting Actinic to the webserver previously but now we've got rather an odd issue where it has trouble locating the cgi-bin folder.

    There is definitely a cgi-bin folder and it does 403 if you try and browse to it (like it should be) however, using Actinic it decides that the folder doesn't actually exist and gives the following error:

    http://i.imgur.com/OkZx9.png

    Any help would be much appreciated.

    Many thanks in advance,

    Martin
    Tags: None
    #2
    It sounds a bit odd.

    Make sure the permission on the cgi-bin are set to 755 (rather than 644) and if the problem still persists you might want us to look at the network settings: Export them, then copy and paste from the txt file into the forum, remembering to overwrite passwords and user names.

    Mike

    PS. Don't use the connection wizard. Enter the network settings that should work and then run a network test.
    -----------------------------------------

    First Tackle - Fly Fishing and Game Angling

    -----------------------------------------

    Comment

      #3
      Yeah, the permissions are all set correctly. It's bizzarre. I've specified a new 'CGI' folder simply called 'cgi' and it's happy to proceed. Although now I have the irritating issue of it being unable to find the Perl location *seethe*.

      Comment

        #4
        Are you still using the connection wizard? If you know what you're doing it's best to avoid it and enter the settings yourself. Then you can run a network test to see what problems there might be.

        Mike
        -----------------------------------------

        First Tackle - Fly Fishing and Game Angling

        -----------------------------------------

        Comment

          #5
          No, I'm now using the Advanced Net settings. I've changed the settings on the server so scripts can run from /cgi/ but to no avail. I mean, it doesn't error 404 on me now but I am getting the following error:

          "The test script failed to execute on the web server. The error could be caused by several things. Check the path to the Perl shell, the CGI script extension, the path to CGI-BIN, and the CGI-BIN URL. This error could also occur if your web site is out of disk space or your web server is not configured to accept POSTs to CGI scripts."

          When I click view response on the window just before that, I get an error 500 from HSphere

          The settings for Sea Chest are as follows:

          HTTPPROXYMODE 0
          HTTPPROXYADDRESS
          HTTPPROXYPORT 80
          HTTPPROXYUSER
          HTTPPROXYPASSWORD
          FTPPROXYMODE 0
          FTPPROXYADDRESS
          FTPPROXYPORT 21
          FTPPROXYUSER
          FTPPROXYPASSWORD
          SCRIPTID 1
          SCRIPTEXT .pl
          SMTPHOST mail.seachest.co.uk
          WEBSITEURL
          IGNOREPASSIVEERRORS true
          USERELATIVECGIURLS false
          PATHTOPERL /usr/bin/perl/
          SSLCATALOGURL https://seachest.co.uk/acatalog/
          SSLCGIBINURL https://seachest.co.uk/cgi/
          SSLPATHFROMCGITOCATALOG ./acatalog/
          SSLCODEBASE ./
          SSLFTPHOST ftp.seachest.co.uk
          SSLFTPUSERNAME
          SSLFTPPASSWORD
          SSLPATHTOCGIBIN /cgi/
          SSLUSEPASSIVEFTP false
          CATALOGURL http://seachest.co.uk/acatalog/
          CGIBINURL http://seachest.co.uk/cgi/
          PATHFROMCGITOCATALOG ./acatalog/
          CODEBASE ./
          FTPHOST ftp.seachest.co.uk
          FTPUSERNAME
          FTPPASSWORD
          PATHTOCGIBIN /cgi/
          USEPASSIVEFTP false
          FTPPATHFROMCGITOCATALOG

          Comment

            #6
            network settings for hsphere have been posted before by jo morecroft at pinbrook:

            HTTPPROXYMODE 0
            HTTPPROXYADDRESS
            HTTPPROXYPORT 80
            HTTPPROXYUSER
            HTTPPROXYPASSWORD
            FTPPROXYMODE 0
            FTPPROXYADDRESS
            FTPPROXYPORT 21
            FTPPROXYUSER
            FTPPROXYPASSWORD
            SCRIPTID 1
            SCRIPTEXT .pl
            SMTPHOST mail.domain.co.uk
            WEBSITEURL http://www.domain.co.uk/
            IGNOREPASSIVEERRORS true
            USERELATIVECGIURLS false
            PATHTOPERL /usr/bin/perl
            USEENHANCEFTP false
            FTPCLIENTTIMEOUT 15000
            FTPRETRYDELAY 3000
            FTPSILENT false
            FTPMAXRETRIES 3
            FTPCONNECTTIMEOUT 25000
            SMTPAUTHREQUIRED false
            SMTPUSERNAME
            SMTPPASSWORD
            CATALOGURL http://www.domain.co.uk/acatalog/
            CGIBINURL http://www.domain.co.uk/cgi-bin/
            PATHFROMCGITOCATALOG ../acatalog/
            CODEBASE ./
            FTPHOST domain.co.uk
            FTPUSERNAME xxx
            FTPPASSWORD XXX
            PATHTOCGIBIN /domain.co.uk/cgi-bin/
            USEPASSIVEFTP true
            FTPPATHFROMCGITOCATALOG /domain.co.uk/acatalog/
            The first things I'd do is:

            1. remove the SSL settings for the moment. They're easily re-applied later.

            2. Path from cgi-bin to acatalog is normally ../catalog/

            3. Jo's settings suggest that when you ftp into the account you might still need to enter the domain in the path. That's also worth checking but could depend on how you have hsphere setup and where the ftp account is defined.

            Mike
            -----------------------------------------

            First Tackle - Fly Fishing and Game Angling

            -----------------------------------------

            Comment

              #7
              And now it appears to be working.

              If you get a chance. Post back with the changes that fixed it for you. It''ll help others with the same problem.

              Mike
              -----------------------------------------

              First Tackle - Fly Fishing and Game Angling

              -----------------------------------------

              Comment

                #8
                I'll see if I can get a remote session and export the settings. I don't think I did anything particularly special, but I think it was potentially just a typo which was holding me up. I'll post a comparison between the settings I've previously posted and the ones which currently work.

                I'm impossibly happy it's working though as I've been going mental trying to get this working!

                Comment

                  #9
                  Code:
                  HTTPPROXYMODE	0
HTTPPROXYADDRESS	
HTTPPROXYPORT	80
HTTPPROXYUSER	
HTTPPROXYPASSWORD	
FTPPROXYMODE	0
FTPPROXYADDRESS	
FTPPROXYPORT	21
FTPPROXYUSER	
FTPPROXYPASSWORD	
SCRIPTID	1
SCRIPTEXT	.pl
SMTPHOST	mail.[domain]
WEBSITEURL	
IGNOREPASSIVEERRORS	true
USERELATIVECGIURLS	false
PATHTOPERL	/usr/bin/perl
SSLCATALOGURL	https://[domain]/acatalog/
SSLCGIBINURL	https://[domain]/cgi-bin/
SSLPATHFROMCGITOCATALOG	../acatalog/
SSLCODEBASE	./
SSLFTPHOST	ftp.[domain]
SSLFTPUSERNAME	******
SSLFTPPASSWORD	******
SSLPATHTOCGIBIN	/cgi-bin/
SSLUSEPASSIVEFTP	false
CATALOGURL	http://[domain]/acatalog/
CGIBINURL	http://[domain]/cgi-bin/
PATHFROMCGITOCATALOG	../acatalog/
CODEBASE	./
FTPHOST	ftp.[domain]
FTPUSERNAME	******
FTPPASSWORD	******
PATHTOCGIBIN	/cgi-bin/
USEPASSIVEFTP	false
FTPPATHFROMCGITOCATALOG
                  These are the settings that are working for my client. I hope that they are of use to anyone else who may be having similar issues.

                  Comment

                  Previous template Next
                  Working...
                  X