Actinic can not locate cgi-bin with my new host

[frostfire]

Our store has been working fine in the past, we have now moved to another host.

Despite speaking to them and changing all sorts of settings Actinic is unable to locate the cg-bin.

This is the message:

Unable to move to the cgi-bin directory "http://frostfirepulse.com/cgi-bin/" on the FTP server.
The specified directory does not exist or you do not have access to the directory.

Attached is the screengrab of the settings, plus the error message plus the location of the cgi-bin in our webspace.

Can anyone help?

thanks

[RuralWeb]

Who are the new hosts - did you check that the hosting package would work with Actinic before you bought it?

[frostfire]

thanks for the prompt response

we actually have bought a dedicated server via liquidweb.com, who are fairly big, so i assumed that we should be ok.

[RuralWeb]

so i assumed that we should be ok.

Hmmm - not always the best plan of action. I would do a search of the forum to see if they are mentioned any where.

[leehack]

Your "path to CGI-BIN" looks incorrect, i would expect to see just "/cgi-bin/" in that field. Having said that as Mal suggests, it is probably to wiser to confirm that your new hosts can actually work with actinic before you spend any more time on it. You could end up chasing yourself in circles.

If you continue trying then i'd also suggest trying to fill out the path to the cgi-bin as viewed by the ftp server as it appears that this field maybe what is firing your error message.

[CymraegKev]

If it's a deidcated machine then it's up to you to make the system work with Actinic, not the hosts - it's effectively your machine.

Ensure you have the correct permissions set for the CGI-BIN directory and also follows Lee's instructions.

Also - make sure you have PerlIS installed if it's a windows box.

Kevin

[frostfire]

Thanks for your comments.

Where can i find the correct permissions for the cgi-bin. The person who is administrating the dedicated server has been through this with me.

I will check now that PerlIS is installed, i am pretty sure he would have checked this.

[leehack]

Ask him what permissions have been set on the cgi-bin. Or ftp to the site, locate the folder and check yourself. Right click on the folder and view properties is how i do it, however i have no idea what you will be using to get there.

[frostfire]

I followed your instructions and have attached the results. Everything looks ok.

[leehack]

Have you tried the other suggestions on changing the loactions in the settings? export your network settings and post them in here, it's easier and you will get more help.

[frostfire]

The following are our settings exported from Actinic. Does this help?


HTTPPROXYMODE 0
HTTPPROXYADDRESS
HTTPPROXYPORT 80
HTTPPROXYUSER
HTTPPROXYPASSWORD
FTPPROXYMODE 0
FTPPROXYADDRESS
FTPPROXYPORT 21
FTPPROXYUSER
FTPPROXYPASSWORD
SCRIPTID 1
SCRIPTEXT .pl
SMTPHOST frostfirepulse.com
WEBSITEURL http://frostfirepulse.com/
IGNOREPASSIVEERRORS true
USERELATIVECGIURLS false
PATHTOPERL /usr/bin/perl
SMTPAUTHREQUIRED false
SMTPUSERNAME
SMTPPASSWORD
CATALOGURL http://frostfirepulse.com/acatalog/
CGIBINURL http://frostfirepulse.com/cgi-bin/
PATHFROMCGITOCATALOG ../acatalog/
CODEBASE ./
FTPHOST frostfirepulse.com
FTPUSERNAME frostfir
FTPPASSWORD xxxxxxxxxx
PATHTOCGIBIN /cgi-bin/
USEPASSIVEFTP false
FTPPATHFROMCGITOCATALOG

[leehack]

Always use the "www." in the URL for starters.

With those settings in mind, what is the error message saying when you run a network test?

[frostfire]

we have tested the cgi as follows:

cgi seems to working fine. You can see this here:
http://frostfirepulse.com/cgi-bin/test.pl
http://frostfirepulse.com/cgi-bin/cgiecho
http://frostfirepulse.com/cgi-bin/ts000001.pl
http://frostfirepulse.com/cgi-bin/cgemail

[Bruce]

Chris,

Couple of things you can check...

If you are on a Windows box, check to see if your path to perl is correct. '/usr/bin/perl' is default for *nix servers but would need the correct path C:\Perl\Bin\Perlis.dll, depends on where and how installed. Also if on a Windows server, change '../acatalog/ to './acatalog/'

Kind regards,

[frostfire]

Bruce, i'll check these immediately, thanks for your help, this is so frustrating.