Question: FileZilla won't connect to server
0
gravatar for sbeek4
4 months ago by
sbeek40
sbeek40 wrote:

I want to upload my files using FTP server FileZilla 3.7.3., but I can't seem to connect to the server. I have tried solving the problem with many experts in my lab who recently used the program to upload files on the galaxy server, but we are not able to solve the problem.

I used usergalaxy.org or ftp://usegalaxy.org as hostname, tried different ports, different computers, and passive and active mode. Strange thing is, I don't get any specific error code.

I got the following response when I try to quickconnect:

Status:                      Resolving address of usegalaxy.org
Status:                      Connecting to 129.114.60.60:21...
Status:                      Connection established, waiting for welcome message...
Response:               220-usegalaxy.org FTP
Response:               
Response:               This FTP server allows users to upload large data to the Galaxy server at:
Response:               
Response:                  https://usegalaxy.org/
Response:               
Response:               Your login uses the same credentials as your Galaxy login - email address and
Response:               password.
Response:               
Response:               Once files are successfully uploaded, the list of files available for importing
Response:               in to a history will be displayed in the regular Upload tool.  For assistance,
Response:               please contact:
Response:               
Response:                  galaxy-bugs@galaxyproject.org
Response:               
Response:               Files uploaded via FTP and not imported to a history within three days will be
Response:               deleted.
Response:               220 FTP Server ready.
Command:               USER XXX@umcutrecht.nl
Response:               550 SSL/TLS required on the control channel
Error:                        Could not connect to server

I also tried connecting via the site manager using the encryption: require explicit FTP over TLS. I now had to accept the license and get this response:

Status:                      Resolving address of usegalaxy.org
Status:                      Connecting to 129.114.60.56:21...
Status:                      Connection established, waiting for welcome message...
Response:               220-usegalaxy.org FTP
Response:               
Response:               This FTP server allows users to upload large data to the Galaxy server at:
Response:               
Response:                  https://usegalaxy.org/
Response:               
Response:               Your login uses the same credentials as your Galaxy login - email address and
Response:               password.
Response:               
Response:               Once files are successfully uploaded, the list of files available for importing
Response:               in to a history will be displayed in the regular Upload tool.  For assistance,
Response:               please contact:
Response:               
Response:                  galaxy-bugs@galaxyproject.org
Response:               
Response:               Files uploaded via FTP and not imported to a history within three days will be
Response:               deleted.
Response:               220 FTP Server ready.
Command:               AUTH TLS
Response:               234 AUTH TLS successful
Status:                      Initializing TLS...
Status:                      Verifying certificate...
Command:               USER sbeek4@umcutrecht.nl
Status:                      TLS/SSL connection established.
Response:               331 Password required for XXX@umcutrecht.nl
Command:               PASS ********
Response:               230 User XXX@umcutrecht.nl logged in
Command:               SYST
Response:               215 UNIX Type: L8
Command:               FEAT
Response:               211-Features:
Response:               EPRT
Response:               EPSV
Response:               MDTM
Response:               SSCN
Response:               TVFS
Response:               MFMT
Response:               SIZE
Response:               PROT
Response:               LANG bg-BG;en-US;es-ES;fr-FR;it-IT;ja-JP;ko-KR;ru-RU;zh-CN;zh-TW
Response:               CCC
Response:               PBSZ
Response:               AUTH TLS
Response:               MFF modify;UNIX.group;UNIX.mode;
Response:               REST STREAM
Response:               MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Response:               UTF8
Response:               211 End
Command:               OPTS UTF8 ON
Response:               200 UTF8 set to on
Command:               PBSZ 0
Response:               200 PBSZ 0 successful
Command:               PROT P
Response:               200 Protection set to Private
Status:                      Connected
Status:                      Retrieving directory listing...
Command:               PWD
Response:               257 "/" is the current directory
Command:               TYPE I
Response:               200 Type set to I
Command:               PASV
Response:               227 Entering Passive Mode (129,114,60,56,117,110).
Command:               MLSD
Error:                        Connection timed out
Error:      Failed to retrieve directory listing

I was wondering whether there is a connection problem on your side? Otherwise do you have any suggestions what to do different? I’m at my wits end.

Admin edit: reformat log (for readability) and modify email address (to protect privacy)

galaxy • 278 views
ADD COMMENTlink modified 4 months ago by Nate Coraor3.1k • written 4 months ago by sbeek40
0
gravatar for Nate Coraor
4 months ago by
Nate Coraor3.1k
United States
Nate Coraor3.1k wrote:

FTP over TLS is required, so your second attempt looks better than the first. It's failing to initiate passive mode, however. Is there a firewall that might be interfering? The FTP server will open a random port between 30000 and 31000 when PASV is issued, so your client will need to be able to connect to that port, and the communications over that port will be encrypted (some firewalls that perform packet inspection do not like this).

Here's a nice explanation on the difference between active and passive FTP, in case that might help. You can use netstat to see which port the FTP server is attempting to connect to.

ADD COMMENTlink modified 8 weeks ago • written 4 months ago by Nate Coraor3.1k
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 75 users visited in the last hour