Change protocol type in settings to: Auth-SSL-Explicit or something like that.

That�s what their FTP info says

In your workspace on your  VEER account there were you must submit you could click on FTP help and you will see this info:



If you plan to upload many files, you can save time by using FTP client software. We suggest FileZilla or Core FTP (for Windows) and Transmit or Fetch (for Mac OS). These programs support the type of secure connection required.

Important: If you use your Workspace (to browse, click buttons, refresh the page, etc.) while your images are uploading by FTP, your images may be corrupted. This is a temporary issue that we are working to resolve.

Host Name
upload.veer.com

Username
Your username is the same as your Veer account sign-in name.

Password
Your password is the same as your Veer account password.

Server Type
FTP over explicit TLS/SSL

worked fine for me yesterday.

Don't forget that you have to use FTP over explicit TLS/SSL - which isn't a default setting and needs to be selected explicitly. You can't set it in Filezilla's quickconnect - you have to set it via Site Manager.

Open filzezilla, go to menu File, then Site Manager. Click New site, type Veer for site name. Then in the right top corner enter upload.veer.com for Host, and select servertype FTEPS - FTP over explicit TLS/SSL

then enter your username (email address you used for Veer) and your password and click Connect

Next time you'll just need to click a little arrow in the top left corner and select Veer from the list that will appear

If anyone here uses FireFTP you can make it work by going to the connection tab and selecting "Auth TLS (Best) from the Security drop down menu.

It was working for me at first but now it has been broken for more than week. FileZilla can log in but it cannot list directories.

Status:   Resolving IP-Address for upload.veer.com
Status:   Connecting to 65.110.167.232:21...
Status:   Connection established, waiting for welcome message...
Response:   220 Veer Marketplace
Command:   AUTH TLS
Response:   234 AUTH command ok. Expecting TLS Negotiation.
Status:   Initializing TLS...
Command:   USER [email protected]
Status:   Verifying certificate...
Status:   TLS/SSL connection established.
Response:   331 Password required for [email protected].
Command:   PASS ********
Response:   230-Directory has 1,073,737,728 bytes of disk space available.
Response:   230 User logged in.
Command:   SYST
Response:   215 Windows_NT
Command:   FEAT
Response:   211-Extended features supported:
Response:    LANG EN*
Response:    UTF8
Response:    AUTH TLS;TLS-C;SSL;TLS-P;
Response:    PBSZ
Response:    PROT C;P;
Response:    CCC
Response:    HOST
Response:    SIZE
Response:    MDTM
Response:    REST STREAM
Response:   211 END
Command:   OPTS UTF8 ON
Response:   200 OPTS UTF8 command successful - UTF8 encoding now ON.
Command:   PBSZ 0
Response:   200 PBSZ command successful.
Command:   PROT P
Response:   200 PROT command successful.
Status:   Connected
Status:   Retrieving directory listing...
Command:   CWD /
Response:   250 CWD command successful.
Command:   PWD
Response:   257 "/" is current directory.
Command:   TYPE I
Response:   200 Type set to I.
Command:   PASV
Response:   227 Entering Passive Mode (65,110,167,232,223,214).
Command:   LIST
Response:   150 Opening BINARY mode data connection.
Error:   Connection timed out
Error:   Failed to retrieve directory listing

Yup, having problems here, too. My upload always fails after approx. half of the file is uploaded, with a 'Connection closed by server' error message.
Tried it with Filezilla and Total Commander over several days now, no difference.

Hi All -

Thanks for reporting these FTP issues.
We've confirmed an issue with the latest versions of FileZilla - the latest patch/hotfix (the app will automatically check for updates on startup) seems to cause this issue resulting in the "failed to retrieve directory listing" error. We weren't able to replicate this error on older versions.

We've notified the folks at FileZilla and are investigating further. In the meantime, we suggest switching to an alternate client. For Windows we've tested and confirmed that CoreFTP is working fine. Fetch is working well for OS X.


- Brian

I hate to disappoint you, Brian, but with CuteFTP I have the same problem: the upload fails about halfway during the transfer.

Could it be that you accidentally set a file size limit of 10MB instead of the allowed 20MB?
It seems to fail always around the 10MB size.

I also have CuteFTP, and I have exactly the same problem.

SmartFTP works fine for me so far.

Another one from CrossFTP:

 CrossFTP Pro 1.53a
 Secure random seed initialized.
[R1] Connect to upload.veer.com
[R1] 220 Veer Marketplace
[R1] AUTH SSL
[R1] 234 AUTH command ok. Expecting TLS Negotiation.
[R1] Negotiating Security Session...
[R1] SSL negotiation successful.
[R1] Encrypting session using cipher TLS_RSA_WITH_AES_128_CBC_SHA
[R1] PBSZ 0
[R1] 200 PBSZ command successful.
[R1] USER [email protected]
[R1] 331 Password required for [email protected].
[R1] PASS (hidden)
[R1] 230-Directory has 1,073,737,728 bytes of disk space available.
[R1] 230 User logged in.
[R1] TYPE I
[R1] 200 Type set to I.
[R1] FEAT
[R1] 211-Extended features supported:
[R1]  LANG EN*
[R1]  UTF8
[R1]  AUTH TLS;TLS-C;SSL;TLS-P;
[R1]  PBSZ
[R1]  PROT C;P;
[R1]  CCC
[R1]  HOST
[R1]  SIZE
[R1]  MDTM
[R1]  REST STREAM
[R1] 211 END
[R1] PWD
[R1] 257 "/" is current directory.
[R1] SYST
[R1] 215 Windows_NT
[R1] PROT P
[R1] 200 PROT command successful.
[R1] PASV
[R1] 227 Entering Passive Mode (65,110,167,232,239,126).
[R1] Opening data connection IP: 65.110.167.232 PORT: 61310
[R1] Connection refused
[R1] Connection refused
[R1] Connection lost.

I can upload smaller files, but larger ones (approx 17MB) always fail.

I'm using CoreFTP and I can't connect, my password seems to be the problem. The last few entries of the log are below - does anyone have an idea as to what I'm doing wrong?

SER AlienCat 
331 Password required for AlienCat. 
PASS ********** 
530 User cannot log in.