Webfusion Network Settings

[beekeeper]

I'm at a very early stage of setting up a website, but am struggling with what ought to be fairly simple. I am using 123-Reg as a host which is part of Webfusion/Pipex I now believe. My question is what are the Network Settings I need? The structure of the root directory on the website is: cgi-bin, logfiles and public_html. It does not seem possible to write directly to the root directory so my settings in the Advanced Network Setwork box are:

Catlog URL: http://www.modernbeekeeping.co.uk/public_html/
CGI_BIN URL: http://www.modernbeekeeping.co.uk/cgi-bin/
Codebase: /public_html/
Path from CGI_BIN to acatlog Directory: ../public_html/acatalog/
Server Host: ftp2.myserverworld.net
Path to CGI-BIN: /cgi-bin/
Path to CGI_BIN to acatlog directory as viewed by the FTP Server: ../public_html/acatalog/

Running Test gives the following messages:

Actinic Mail Test completed successfully
server: passed
connection: failed
sockets: passed
communications: failed
authorisation: failed
message: Connection refused

Then this message appears:

Your Catalog URL appears to be invalid. The files uploaded to the given 'Path from cgi-bin to acatalog directory', can not be downloaded via the browser on the given Catalog URL. These two access routes don't point to the same destination on the server.

The site has uploaded and the acatlog directory has been created under public_html but clearly things are not right.

Does anyone know what the network setting should be? The Webfusion Technical Support Line could not help.

[wjcampbe]

Try

Catlog URL: http://www.modernbeekeeping.co.uk/acatalog/
CGI_BIN URL: http://www.modernbeekeeping.co.uk/cgi-bin/
Codebase: ./
Path from CGI_BIN to acatlog Directory: ../public_html/acatalog/
Server Host: ftp2.myserverworld.net
Path to CGI-BIN: /cgi-bin/
Path to CGI_BIN to acatlog directory as viewed by the FTP Server:



When you arrive on the website with http (browser) you arrive already inside the public_html folder. This helps keep the information in cgi-bin and logfiles inaccesible to the casual browser.

[leehack]

From the settings you have provided, i'm presuming that you are hosting on a windows server, if so you will undoubtedly find Actinic works much better with a Unix advanced package through webfusion. Your hosting provider should be able to change this for you.

[beekeeper]

Thanks

the host is on Linux so hopefully should be OK.

VMT to Bill for his suggestion. Using the form <website URL>/acatlog/ for Catalog URL works, even though the directory /acatalog/ is actually nested below /publix_html/. The site has now uploaded succesfully and the scripts work.

My next problem is to get the e-mail to work - I may be back!

John