Announcement

Collapse
No announcement yet.

Trying to upload site.

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

    Trying to upload site.

    Hello to the Community,

    Having had to move to new Hosting company, I am now trying to upload my site in order to test if it works and transactions are possible.

    When I go to: Web/update website. The program starts to check and send files. When it gets to: sending base files-it stalls and I get an error message:

    Error accessing the cgi-bin.

    Possible Cause:
    The directory does not exist on the remote server
    The permissions on the directory on the
    remote server are locked
    The wrong Path to the CGI-BIN is specified in your
    web site details in
    the Business Settings
    Recommendation:
    Abort
    Resolution:
    Run the Web | Configure Web Site Details command to verify your setup
    Create the cgi-bin directory on the remote server
    Correct the permissions on the cgi-bin directory on
    the remote server

    From this I guess it's a problem with my cgi-bin!
    My network settings are:

    HTTPPROXYMODE 0
    HTTPPROXYADDRESS
    HTTPPROXYPORT 80
    HTTPPROXYUSER
    HTTPPROXYPASSWORD
    FTPPROXYMODE 0
    FTPPROXYADDRESS
    FTPPROXYPORT 21
    FTPPROXYUSER
    FTPPROXYPASSWORD
    SCRIPTID 1
    SCRIPTEXT .pl
    SMTPHOST 69.44.19.51
    WEBSITEURL http://www.flareshoes.com
    IGNOREPASSIVEERRORS false
    USERELATIVECGIURLS false
    PATHTOPERL /usr/bin/perl
    SMTPAUTHREQUIRED false
    SMTPUSERNAME
    SMTPPASSWORD
    SSLCATALOGURL https://www.flareshoes.com/
    SSLCGIBINURL https://www/flareshoes.com/cgi-bin/
    SSLPATHFROMCGITOCATALOG ../acatalog/
    SSLCODEBASE ./
    SSLFTPHOST www.flareshoes.com
    SSLFTPUSERNAME ####
    SSLFTPPASSWORD ####
    SSLPATHTOCGIBIN /usr/local/psa/home/vhosts/flareshoes.com/cgi-bin/
    SSLUSEPASSIVEFTP true
    CATALOGURL http://www.flareshoes.com/acatalog/
    CGIBINURL http://www.flareshoes.com/cgi-bin/
    PATHFROMCGITOCATALOG /httpdocs/acatalog/
    CODEBASE ./
    FTPHOST www.flareshoes.com
    FTPUSERNAME ####
    FTPPASSWORD ####
    PATHTOCGIBIN /cgi-bin/
    USEPASSIVEFTP true
    FTPPATHFROMCGITOCATALOG



    Can anyone trouble shoot my problem(s)
    Thanks.

    Taiwo

    #2
    Hi there

    I see from your network setup your are using split ssl. Plus checking https://www.flareshoes.com/, this should show you site, but it shows a holding page.

    You need to setup a symbolic link between the secure /acatalog/ folder and the insecure /acatalog/ folder. Therefore if you put any information into the insecure /acatalog/ folder, you should see this in the secure /acatalog/ folder.

    I have also checked and seen you are using Plesk, one of our support team had been trying to help our webhosting partner to work with this and we could not achieve it. The reason being, is that there will be two different owner of the scripts which results in an order lock error or cannot open .session file.

    I'm afraid this might happen on your as well, in which case, the only thing you can do is to either enable the inbuilt encryption, get actinic shared ssl or go through a payment gateway (ie Worldpay).

    Kind Regards
    Nadeem Rasool
    SellerDeck Development

    Comment


      #3
      Hi
      Are you saying that actinic cannot run on PLESK?


      Thanks

      Comment


        #4
        Steve,

        Actinic does work on Plesk servers, you will however have to use a PSP like worldpay or such for payments.

        Can other users who have stores setup via a Plesk control post here please.

        Kind regards,
        Bruce King
        SellerDeck

        Comment


          #5
          Steve,
          We have configured many sites on Plesk in the past with and without SSL's configured without any incident.
          Judging by the holding page you have on your domain I would suggest that you check that the unique IP that should have been assigned with the SSL certificate has been correctly configured in the DNS file.
          Also I would suggest that the

          SSLPATHTOCGIBIN /usr/local/psa/home/vhosts/flareshoes.com/cgi-bin/

          is incorrect.

          SSLPATHTOCGIBIN /cgi-bin/

          would seem to be more likely.
          This indeed may be the source of your error.

          Again, dependent on server configuration, however

          SSLCATALOGURL https://www.flareshoes.com/

          would suggest to me, based on the other settings, that it should be

          SSLCATALOGURL https://www.flareshoes.com/acatalog/

          and depending on which version of Plesk you are using you can specify the httpdocs and httpsdocs folder to be located in the same physical folder, resolving a lot off separate SSL folder issues that actinic has had in the past.
          Fergus Weir - teclan ltd
          Ecommerce Digital Marketing

          SellerDeck Responsive Web Design

          SellerDeck Hosting
          SellerDeck Digital Marketing

          Comment


            #6
            Hi, you say you have set up many sites on plesk, but have you ever done any where the set up is like

            http://mydomain.com
            https://mydomain.secureserveruk.com

            I understand how it works when the secure server is the same domain as the normal server when setup with plesk as you can configure both to reside in the same directory, but when they are different domains pointing to different folders is when I have problems because, i assume, from what I have read the limitations of plesk.

            could you maybe manually configure the domain in the httpd.conf file so it points the secure domain to the same directory as the main domain? or would this just confuse plesk?

            thanks

            J

            Comment


              #7
              Hi J,

              You can indeed do this. This in effect fools the browser into thinking that it is using separate folders when in fact it is not.
              As long as the mydomain.secureserveruk.com has an A record correctly configured to the same IP as http://mydomain.com and correctly set up in
              httpd.conf then it should work without incident.
              I would always double check with your hosting administrator regarding the correct procedure for implementing this.

              An example of this can be seen at http://www.lapcase.co.uk using https://lapcase.secured-area.co.uk/ when going to checkout.
              Fergus Weir - teclan ltd
              Ecommerce Digital Marketing

              SellerDeck Responsive Web Design

              SellerDeck Hosting
              SellerDeck Digital Marketing

              Comment

              Working...
              X