After updating my store I have always exported the store to my desktop and manually uploaded the files to my server using CoreFTP. Everytime I have ever used SCC's FTP it gets three quarters of the way and then I get an error. Usually I can get it to upload all the files but I have to run it 2 or 3 times to get all the way there. I have been using FTP progs for years and all my settings are spot on, its just that I get some kind of connection issue half way through. I have a 20meg Optical connection and can download at speeds up to 26meg which is a lot more than obviously needed so I have to contune using an external FTP prog. Has anyone else encountered unreliable connections with the internal FTP, or it is just me?
Thanks guys...

i have tried SCC's FTP and works flawlessy !

What I find - not often, but now and again... if I am really fast with making the last couple of changes to something in the store and then make a really fast switch to upload... at the end of the upload process I get a "failed" message. But if I wait a few seconds before upload, everything all goes through smoothly.

The first time I uploaded my store I got an error message about 85% through the process. Then I tried again and it didn't hiccup on the image file as in the first try but on an image file a little further on. 3rd try it told me that my anti virus or a firewall was blocking--I had been using passive mode.

I just waited a little while and tried again and it went through completely and uploaded perfectly. I have made changes and uploaded about 4-5 times since last week when I did that first upload. All is working fine. It is so easy using the internal upload!

Hi Sh00ta,

Generally, when you have problems connecting using the FTP Protocols included with our software, there are a number of common causes that we always like to look into first. We've collected them into a list for your convenience:

1.) Ensure that you do NOT have your server address (also known as domain, hostname, FTP address, or some combination thereof) prefixed with any of the following: www., ftp., or HTTP://. It should look something like this: "yourdomainname.com".

2.) Ensure that, unless you have been explicitly instructed otherwise, you have not inserted anything in the proxy settings of the FTP Protocol. Proxy settings are an advanced security feature, and putting anything but the absolute precise settings needed in here will cause the program to lag and time out.

3.) Generally, you are going to want to enable Passive Mode if presented with the option. This option controls how you connect to the server (and how it connects to you), and will often help if you can connect to a server but find yourself unable to upload (or unable to see any files once you upload).

4.) Before connecting, you'll want to disable any security software, firewall software, or antivirus software. This will usually be the culprit if you're getting timeout errors or other unspecified errors. In almost every case, it's a good idea to disable these programs when you plan to upload.

If you're still experiencing any issues after going through these four options, please write us back!

Without the ftp. prefix before my server address is will not even connect. All ftp progs I have ever used have the prefix ftp. before your domain address and then the domain address with no prefix as the username. It connects fine this way but rocks out three quarters of the way

Not all ftp servers require the ftp prior to domain name.

Ditto Tom, mine also does not require this, but I do realize many do require that, yet either way I wouldn't think that would stop you from uploading... not sure though.

Mine only uploads with the ftp in front. I tried the other methods and they wouldn't work for me at all.

I pulled this out of the help manual:

Server
The TCP/IP hostname of your FTP server. It should be in the form of an IP address, your domain name (e.g. yourdomain.com), or your domain name preceded by ftp. (e.g. ftp.yourdomain.com). Do not include ftp:// or any directory name such as ftp.yourdomain.com/mysite, because these are invalid TCP/IP hostnames. It is up to your Web hosting company to assign your FTP server hostname, so you will need to find out from them what it is.

Examples of valid hostnames
ftp.mysite.com
24.24.100.100
mysite.com

What you should not do, according to the instructions... is add forward slashes after your ftp.

My details are as follows-

server- ftp.mywebsite.com
username- mywebsite.com

Connects flawlessley everytime so the details are obviously correct but perhaps only 3 times out of 10 will it upload all the way from empty. One thing i have noticed though is if im running just an update and there are only a few changes it flies by and works great it just struggles from empty. Iv tried on both my work on my home machine, one with a 2meg connection and the other with a 20meg. Iv tried firewalls on and off, tried different username credentials but I cannot get any different results. I gave up a long time ago for the same reason, hence coreftp but now im determined to find a solution