• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

The site cannot be published to the specified location

Cnote

Basic Pleskian
I'm getting this message now on all sites.

"The site cannot be published to the specified location.
Cannot find site files at http://xxxxxxxxxx.com/. The specified site URL does not match the FTP settings."

I have tested FTP info and they all work with 3rd party FTP programs as well as simply using FTP from command prompt.

All of my customers are complaining, I don't know what to do.

I've tried removing/recreating domains. Removing and recreating SB accounts. None of them want to work.

Log file shows.

Action status: 2; Target: /Admin/Site/Edit; Messages: The site cannot be published to the specified location.
System 11/24/2007 12:03:15 PM admin 000.000.000.000 Cannot find published site files at 'http://xxxxxxxxxx.com/'. Publication settings URL does not match the specified FTP settings....

000.000.000.000 (not my actual server IP

I have sitebuilder installed on one server and it publishes to another server.

Using SB 4.0.0 (2007062700)
 
I've been to that first page before... pretty basic stuff.

The strange thing now is all of my sites are giving me the same error.
"The site cannot be published to the specified location.
Cannot find site files at http://xxxxxxxxxx.com/. The specified site URL does not match the FTP settings."

which doesn't make sense because I had just reset a username and password for one of my clients the day before and it worked fine, but now it isn't.
 
Let's try to configure publishing settings one more time.
If you use FTP publishing mode:

Publishing mode: FTP

Host (IP address or DNS name): IP address or hostname (which should be resolved correctly). This is IP address for remote FTP server (it can be the same server where Sitebuilder installed) to which publication should be done.

Port: by default 21 (if you use custom port on FTP this value should be changed).

Login: FTP user name. This FTP user should be registered on remote FTP server to which publication should be done.

Password: make sure that password is correct. Just try to log into the server via FTP under this FTP user and specified password.

Web site URL: URL for website to which data is going to be published. This web site should be resolved to the same IP address which is specified in Host field.

Working directory: this is path for websites files. This is the same path which you need to type after logging under FTP user to get to site files directory.

For example, my test FTP user has home directory /var/www/vhosts/test.com
but site files are stored into httpdocs/ folder /var/www/vhosts/test.com/httpdocs, so in this case I will specify

Working directory: httpdocs/
Web site URL: http://test.com

If you still have some problems with this try to contact with support team, as it will require checking situation directly in Sitebuilder CP.
 
Host (IP address or DNS name): IP address or hostname (which should be resolved correctly). This is IP address for remote FTP server (it can be the same server where Sitebuilder installed) to which publication should be done.
IP address is what I use and it resolves correctly.

Port: by default 21 (if you use custom port on FTP this value should be changed).
Port 21 is what is being used.

Login: FTP user name. This FTP user should be registered on remote FTP server to which publication should be done.
User is registered on the remote server.

Password: make sure that password is correct. Just try to log into the server via FTP under this FTP user and specified password.
FTP username and password tested and worked.

Web site URL: URL for website to which data is going to be published. This web site should be resolved to the same IP address which is specified in Host field.
URL resolves to the same IP address as host.

Working directory: this is path for websites files. This is the same path which you need to type after logging under FTP user to get to site files directory.For example, my test FTP user has home directory /var/www/vhosts/test.com
but site files are stored into httpdocs/ folder /var/www/vhosts/test.com/httpdocs, so in this case I will specify Working directory: httpdocs/
Web site URL: http://test.com
Working directory is httpdocs (double checked)

I tried submitting a support ticket through the admin panel of SB but I got a message saying that my license for support has expired and that SWsoft would have to charge a fee for service.

Not sure what else to do.

Cnote
 
In this case I can check it for you if you provide me with IP address, web site URL and FTP access to this site. Change temporary FTP password and let me know the details. I will check it from my side.
You can send this information via private message, for example, to make it more secure.
 
Started getting this same error (1st time out of 20 sites), any resolution?

Thanks!
 
Yeah, the site/s that I was having problems with used to reside on the same server as SB is installed on. Since then I have aquired an additional server that sites get published to.

To fix my problem I had to add a line to the /etc/host file

xxx.xxx.xxx.xxx domain.com

so the ip address that the target domain resolves to and the domain name.

I think it had something to do with the fact that the domain used to be on a different server and SB was using some cached information.

Hope this helps you.

good luck.... and thanks to Dmitry for the help on this.
 
Found the fix for our problem, turn off safe mode for the site.
 
I'm getting the exact same error. no clue what to do.

Error: The site cannot be published to the specified location.
An error has occurred during publishing via FTP. Please contact the server administrator.

the information works correctly IP resolves correctly, FTP user and password works

[root@heracles php]# ftp
ftp> open XX.53.XX.162
Connected to XX.53.XX.162.
220 ProFTPD 1.3.0 Server (ProFTPD) [XX.53.XX.162]
500 AUTH not understood
500 AUTH not understood
KERBEROS_V4 rejected as an authentication type
Name (XX.53.XX.162:root): darlex
331 Password required for darlex.
Password:
230 User darlex logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> ls
227 Entering Passive Mode (XX,53,XX,162,224,146).
150 Opening ASCII mode data connection for file list
drwxr-x--- 5 darlex psaserv 4096 May 14 2007 anon_ftp
drwxr-x--- 2 darlex psaserv 4096 Jun 6 2005 cgi-bin
drwxr-x--- 2 root psaserv 4096 Mar 12 19:32 conf
drwxr-xr-x 2 root psaserv 4096 Jun 6 2005 error_docs
drwxr-x--- 20 darlex psaserv 4096 Mar 12 19:33 httpdocs
drwxr-x--- 4 darlex psaserv 4096 Jun 6 2005 httpsdocs
drwxrwx--- 2 apache psacln 4096 May 21 2007 mivadata
drwxr-x--- 2 root psaserv 4096 Mar 12 19:32 pd
drwx------ 2 darlex root 4096 Nov 17 2006 private
dr-xr-x--- 7 root psaserv 4096 May 14 2007 statistics
drwxr-xr-x 2 root psaserv 4096 May 14 2007 subdomains
drwxr-xr-x 2 root psaserv 4096 May 14 2007 web_users
226-Transfer complete.
226 Quotas off
ftp> close
221 Goodbye.
ftp> quit
[root@heracles php]#

not a single clue why sitebuilder is not publishing the sites.
 
I'm getting the exact same error. no clue what to do.

Error: The site cannot be published to the specified location.
An error has occurred during publishing via FTP. Please contact the server administrator.

the information works correctly IP resolves correctly, FTP user and password works

Did you change servers/hosts? In my case I used to publish to the same server that SB was installed on. Then I added a server and changed the hosts in SB. That was fine until I tried publishing to one of the old sites even though I had migrated them and changed the DNS info for the domain. I had to add a line to the hosts file on the server that had been used for both SB and published sites.

the line was domain.xxx x.x.x.x

so, domain, then ip of the domain.

Hope that helps..

you may also want to make sure safemode is turned off for the domain you are trying to publish to.
 
Did you change servers/hosts? In my case I used to publish to the same server that SB was installed on. Then I added a server and changed the hosts in SB. That was fine until I tried publishing to one of the old sites even though I had migrated them and changed the DNS info for the domain. I had to add a line to the hosts file on the server that had been used for both SB and published sites.

the line was domain.xxx x.x.x.x

so, domain, then ip of the domain.

Hope that helps..

you may also want to make sure safemode is turned off for the domain you are trying to publish to.

The problem is present only with the sites of that user.(that user has 2 sites under the account)
 
Yes, I got it....I forgot about this situation, although met it before. Thank you for the posting the whole story. This could help someone else to avoid this situation in future.
 
Back
Top