Facebook
Twitter
K
KirrilyR
Guest
Hello,
I am from a company in Australia that has multiple clients with websites using Sitebuilder, supplied by Web24.
We have been running the Sitebuilder for about 2 years now with no errors... now we have one that has caused ALL of our sites to fail to publish.
The error we get when attempting to publish via Sitebuilder is:
The site cannot be published to the specified location.
Cannot connect to the host via FTP.
The logs in Plesk say:
Creation date 2/22/2010 10:01:29 AM
Level Error
Source System
Source System
User name admin
IP address xx.xx.xx.xxx
Requested URL /Wizard/Publish
Referrer URL http://sitebuilder.companyname.hosting24.com.au/Wizard/Publish
User agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729)
Message Can't connect to the host 'xxx.xxx.xxx.xxx'
Site name: xx
Site owner: xx
Publication settings target: ftp://[email protected]/httpdocs/
Publication settings url: http://xx.com.au/
Basically, we get this error on all of our sites... And on one sitebuilder website that has previously had the eshop removed before publishing is giving an Internal Sitebuilder Error: Unable to find container for module instance when just going to the Pages section of the Sitebuilder, but I have read a previous thread that states that this is because it is still looking for the eshop which doesn't exist anymore, but the fix did not make any sense to me!
We haven't changed any of the FTP details, haven't changed our servers or upgraded anything, haven't touched a thing. This error has just popped up out of no where, and our hosting company will not provide support as they are only the resellers... which is very frustrating for us, as our clients are beginning to get aggravated that they cannot update their website.
Any help would be fantastic, and please speak in lamens terms as we are not very technical when it comes to databases and running all sorts of tests, etc.
We just need some professional help to get this error sorted out so that we can begin publishing sites again.
Thank you!
I am from a company in Australia that has multiple clients with websites using Sitebuilder, supplied by Web24.
We have been running the Sitebuilder for about 2 years now with no errors... now we have one that has caused ALL of our sites to fail to publish.
The error we get when attempting to publish via Sitebuilder is:
The site cannot be published to the specified location.
Cannot connect to the host via FTP.
The logs in Plesk say:
Creation date 2/22/2010 10:01:29 AM
Level Error
Source System
Source System
User name admin
IP address xx.xx.xx.xxx
Requested URL /Wizard/Publish
Referrer URL http://sitebuilder.companyname.hosting24.com.au/Wizard/Publish
User agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 (.NET CLR 3.5.30729)
Message Can't connect to the host 'xxx.xxx.xxx.xxx'
Site name: xx
Site owner: xx
Publication settings target: ftp://[email protected]/httpdocs/
Publication settings url: http://xx.com.au/
Basically, we get this error on all of our sites... And on one sitebuilder website that has previously had the eshop removed before publishing is giving an Internal Sitebuilder Error: Unable to find container for module instance when just going to the Pages section of the Sitebuilder, but I have read a previous thread that states that this is because it is still looking for the eshop which doesn't exist anymore, but the fix did not make any sense to me!
We haven't changed any of the FTP details, haven't changed our servers or upgraded anything, haven't touched a thing. This error has just popped up out of no where, and our hosting company will not provide support as they are only the resellers... which is very frustrating for us, as our clients are beginning to get aggravated that they cannot update their website.
Any help would be fantastic, and please speak in lamens terms as we are not very technical when it comes to databases and running all sorts of tests, etc.
We just need some professional help to get this error sorted out so that we can begin publishing sites again.
Thank you!
