The CGI scripts are not executing properly on the server.

[webdesignhelper]

i have just moved to a new server, but when i run the test to check my settings i always get:

The CGI scripts are not executing properly on the server .... etc

but when i run the wizard to get the new settings it always fails on the perl path page, but the path to perl in there is correct, it has been checked and double checked with my server techs ?

I have manually changed the rest of the settings in the set-up but no matter what i do it will not accept the path to perl ?

HTTPPROXYMODE 0
HTTPPROXYADDRESS
HTTPPROXYPORT 80
HTTPPROXYUSER
HTTPPROXYPASSWORD
FTPPROXYMODE 0
FTPPROXYADDRESS
FTPPROXYPORT 21
FTPPROXYUSER
FTPPROXYPASSWORD
SCRIPTID 25
SCRIPTEXT .pl
SMTPHOST localhost
WEBSITEURL http://www.stop-go.co.uk/
IGNOREPASSIVEERRORS true
USERELATIVECGIURLS false
PATHTOPERL /usr/bin/perl
USEENHANCEFTP true
FTPCLIENTTIMEOUT 15000
FTPRETRYDELAY 3000
FTPSILENT false
FTPMAXRETRIES 3
FTPCONNECTTIMEOUT 25000
SMTPAUTHREQUIRED false
SMTPUSERNAME
SMTPPASSWORD
CATALOGURL http://www.stop-go.co.uk/acatalog/
CGIBINURL http://www.stop-go.co.uk/cgi-bin/
PATHFROMCGITOCATALOG /httpdocs/acatalog/
CODEBASE ./
FTPHOST 91.192.194.102
FTPUSERNAME ******
FTPPASSWORD ******
PATHTOCGIBIN /cgi-bin/
USEPASSIVEFTP true
FTPPATHFROMCGITOCATALOG /httpdocs/acatalog/



on the server i have httpdocs and cgi-bin in the same location, with the acatalog folder inside the httpdocs folder.

[Duncan Rounding]

Who's your host and what package do you have?

[webdesignhelper]

i have a dedicated managed server from: www.cwcs.co.uk running plesk.

[Duncan Rounding]

Can you place the cgi-bin folder on the same level as the acatalog folder and then try again?

[fergusw]

I'd suggest that there is an issue with the server configuration.

If you have plesk control panel access then within the hosting setup screen check to make sure that cgi-bin checkbox is selected for this domain.

The server is basically not executing nor returning anything back to the browser when cgi scripts are called.
Also, double check the permissions on the cgi-scripts as well - 755

[meden]

You also will need to ensure that PERL is enabled through the Plesk control panel

[webdesignhelper]

all .pl scripts are set to 755, both cgi and perl support are switched on in the plesk control panel for the domain.

this has worked in the past with the cgi-bin on the same level as the httpdocs folder ?

[jont]

PATHFROMCGITOCATALOG /httpdocs/acatalog/


Is that right?

[webdesignhelper]

what else could it be ?

[jont]

That is the path from the cgi to the actalog is typically

../acatalog/

as they at the same level on the server.

you have used the same setting as per the FTP setting I think (as seen by the server)

[dscontroller]

This site is located on a Plesk server.

Does this help?

Regards,
David

[Paul Bulpit]

And this one, see attached.

I had big problems, same as yours, when first going on to this server (Plesk) - the CGI-BIN does NOT reside at the same level as the web root, but appears to do so when online. The host said that this was for security reasons.

You could perhaps try: (export your own network settings first)

Edit this textfile with your domain and ftp username & password, then use [Import] in Network Settings to install it, then try Network Test.

Alternatively, the answer I found originally was to use the Wizard to point to the directories.

[Paul Bulpit]

Is that right?

I believe so, mine's the same.




.

[jont]

(Plesk) - the CGI-BIN does NOT reside at the same level as the web root, but appears to do so when online. The host said that this was for security reasons.

Never knew that (not hosted on Plesk before) but good to know for the future.

[Paul Bulpit]

After a lot of bother, we got this from the Host:

CGI scripts need to be executed from /var/www/vhosts/domain.com/cgi-bin/ - i.e. not /var/www/vhosts/domain.com/httpdocs/cgi-bin. This is for security, although the public URI is still domain.co.uk/cgi-bin/ca000001.pl

My hosting agent said:

I didn’t realise until he pointed it out. Sorry for that, the real cgi-bin folder is “off web space” so that script cannot be run directly from the address bar, only by the Web Site.

(Though I'm not sure that's correct)


Paul

[webdesignhelper]

still no luck, my settings are now:

HTTPPROXYMODE 0
HTTPPROXYADDRESS
HTTPPROXYPORT 80
HTTPPROXYUSER
HTTPPROXYPASSWORD
FTPPROXYMODE 0
FTPPROXYADDRESS
FTPPROXYPORT 21
FTPPROXYUSER
FTPPROXYPASSWORD
SCRIPTID 119
SCRIPTEXT .pl
SMTPHOST localhost
WEBSITEURL http://www.stop-go.co.uk/
IGNOREPASSIVEERRORS true
USERELATIVECGIURLS false
PATHTOPERL /usr/bin/perl
USEENHANCEFTP true
FTPCLIENTTIMEOUT 15000
FTPRETRYDELAY 3000
FTPSILENT false
FTPMAXRETRIES 3
FTPCONNECTTIMEOUT 25000
SMTPAUTHREQUIRED false
SMTPUSERNAME
SMTPPASSWORD
CATALOGURL http://www.stop-go.co.uk/acatalog/
CGIBINURL http://www.stop-go.co.uk/cgi-bin/
PATHFROMCGITOCATALOG /var/www/vhosts/stop-go.co.uk/httpdocs/acatalog/
CODEBASE ./
FTPHOST ftp.stop-go.co.uk
FTPUSERNAME ******
FTPPASSWORD ******
PATHTOCGIBIN /cgi-bin/
USEPASSIVEFTP true
FTPPATHFROMCGITOCATALOG /httpdocs/acatalog/

[Paul Bulpit]

Try:

Advanced Network Setup | Wizard

Check the box "Confirm Each Setting", [Next]

Work through following screens (carefully, double-checking) until you get to:

(Popup) 'Exploring the Directories on your website' followed by 'Directories'

Click on the top CGI-BIN (should be the second one down?) then click the top >> button.

Click on 'httpdocs' then the bottom >> button.

Follow the next screens, when you get to 'Path' click on 'httpdocs' and >>

When finished, run 'Test'

[Paul Bulpit]

I notice in your posted settings you have

SCRIPTID 119 which came from my file. Your script ID may be different.

Sorry.

[fergusw]

Has this site ever been working?

Your
http://www.stop-go.co.uk/acatalog/error.err
page shows some "XML Cart malformed" errors which would indicate that the actinic site was able to progress to the checkout at some point (last tiem being 30th Jan).
If this is the case then your host needs to look at what might have changed. With PLESK control panels occasionally the problem lies in the underlying APpache server and cannot be changed/seen via the Plesk control panel.

[webdesignhelper]

i've tried the wizard but it always stops at the perl path page, i know the path is correct but it always says it not and will not let me past that page.

[fergusw]

I really think it is worthwhile speaking to you host directly here. This is almost definately a hosting configuration issue. Your initial settings looked fine for a Unix server.