Can't Connect

Need help with FileZilla Client? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
gcrawford
500 Command not understood
Posts: 2
Joined: 2020-01-08 19:25
First name: Gavin
Last name: Crawford

Can't Connect

#1 Post by gcrawford » 2020-01-08 19:52

I've been trying to figure out why I can't connect to any of my sites, but haven't been able to figure it out. I wasn't having any issues until 3 weeks or so, when I did 2 things: changed ISP, and updated to a new version of Filezilla.

I was on the phone for over an hour today with my ISP, thinking it might be a firewall setting in my new modem/router. But that didn't help.

So now I'm thinking it might be an issue with updating to the newest version of Filezilla. I typically have used Plain FTP in the past, and see that FTP over TLS is now required in the new version, so I ran a test (results below). The only warning I received was in regards to an IPv6 address (Warning: The entered address does not resolve to an IPv6 address.). Is this possibly the issue? Any help would be greatly appreciated!


https://ftptest.net/
Test your FTP server. Quick and easy.


Test log

Status: Resolving address of www.signsa2.com

Status: Connecting to 23.111.148.108

Warning: The entered address does not resolve to an IPv6 address.

Status: Connected, waiting for welcome message...

Reply: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

Reply: 220-You are user number 8 of 50 allowed.

Reply: 220-Local time is now 14:36. Server port: 21.

Reply: 220-This is a private system - No anonymous login

Reply: 220-IPv6 connections are also welcome on this server.

Reply: 220 You will be disconnected after 15 minutes of inactivity.

Command: CLNT https://ftptest.net on behalf of 2601:40d:4301:3480:d037:5b3b:de54:1326

Reply: 530 You aren't logged in

Command: AUTH TLS

Reply: 234 AUTH TLS OK.

Status: Performing TLS handshake...

Status: TLS handshake successful, verifying certificate...

Status: Received 3 certificates from server.

Status: cert[0]: subject='OU=Domain Control Validated,OU=PositiveSSL,CN=velocity.myhostdns.com' issuer='C=US,ST=TX,L=Houston,O=cPanel\5c, Inc.,CN=cPanel\5c, Inc. Certification Authority'

Status: cert[1]: subject='C=US,ST=TX,L=Houston,O=cPanel\5c, Inc.,CN=cPanel\5c, Inc. Certification Authority' issuer='C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Certification Authority'

Status: cert[2]: subject='C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Certification Authority' issuer='C=SE,O=AddTrust AB,OU=AddTrust External TTP Network,CN=AddTrust External CA Root'

Command: USER signsa2

Reply: 331 User signsa2 OK. Password required

Command: PASS ***********

Reply: 230 OK. Current restricted directory is /

Command: SYST

Reply: 215 UNIX Type: L8

Command: FEAT

Reply: 211-Extensions supported:

Reply: EPRT

Reply: IDLE

Reply: MDTM

Reply: SIZE

Reply: MFMT

Reply: REST STREAM

Reply: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;

Reply: MLSD

Reply: AUTH TLS

Reply: PBSZ

Reply: PROT

Reply: UTF8

Reply: TVFS

Reply: ESTA

Reply: PASV

Reply: EPSV

Reply: SPSV

Reply: ESTP

Reply: 211 End.

Command: PBSZ 0

Reply: 200 PBSZ=0

Command: PROT P

Reply: 200 Data protection level set to "private"

Command: PWD

Reply: 257 "/" is your current location

Status: Current path is /

Command: TYPE I

Reply: 200 TYPE is now 8-bit binary

Command: PASV

Reply: 227 Entering Passive Mode (23,111,148,108,219,76)

Command: MLSD

Error: Connection timed out

gcrawford
500 Command not understood
Posts: 2
Joined: 2020-01-08 19:25
First name: Gavin
Last name: Crawford

Re: Can't Connect

#2 Post by gcrawford » 2020-01-08 20:10

Finally got it! Turns out I needed some different settings from the webhost since the updated version of Filezilla only allows TLS. :)

User avatar
boco
Contributor
Posts: 25195
Joined: 2006-05-01 03:28
Location: Germany

Re: Can't Connect

#3 Post by boco » 2020-01-09 03:20

Correction: Plain FTP is still possible, however, by default (Auto setting), FTP over TLS is attempted first. If the server does not support FTPS, a fallback to plain FTP occurs.

The third case, experienced by yourself, results in a connection failure (and rightfully so). The server offers FTPS support, but lacks proper configuration. Good to hear it is now working, but ideally, a correct configuration from the start would have been the best. Sounds a bit strange that nobody else had complained, before.
### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

Post Reply