Help...Server problems

[Designer1]

I receive the attached error when connecting to my web server.

Everything seems to go fine until I attempt to designate the actinic files folder.

Anyone know what to do?

Thanks

[wjcampbe]

Try setting your root to / and see if that allows you to create an acatalog folder at the same level as /httpdocs. If not, tell us who the webhost is and perhaps someone can share the setup they use on that same host provider.

Can you confirm you are not on a windows server?

[I-CC]

Would suggest the ftp path would be

CGI-BIN Directory = /httpdocs/cgi-bin

assuming you have a cgi-bin in your public web area and the web root looks fine....

Actinic needs to have cgi-bin files which are web accessible, which when beneath the /httpdocs folder is outside of that access area.

Should do it...

[Designer1]

Server upload - Becoming exasparated...



I have had my hosting provider configure the site to accept Actinic.

As mentioned previously, I use the wizard and it recognises all of the folders.

When I try to go to next stage - I receive an 'error sending HTTP request to web server - perhaps web server is down' type error message.

It seems to be a Windows NT IIS server. I am uploading using Virgin Broadband on a wireless network with a D-LINK G640T wireless router/modem.

Help...

[wjcampbe]

Do you have the firewall operational on the G604T? If yes, try switching that off and leaving just the NAT running.

You can also open a command window and use 'ping mydomain.co.uk' to make sure the server really is not down.

When you say your host has set you up for Actinic, did you refer them to the instructions for IIS5 in the Actinic Advanced Guide?

[Designer1]

server

Hi - yes I do have a firewall running...

I tried an upload to the Actinic trial server and had no specific problems - store uploaded fine.

I have sent also the server setup details.

[wjcampbe]

OK, if you uploaded to the Actinic trial, then your 604T settings are good (I use one too - only niggle I have with it is the log ignores the real date ).

Everything seems to be pointing to the webhost not providing the virtual link to cgi, or a permissions issue.