I am receiving an error after changing our public IP. I have updated the ip in the server config and updated the ip in the NAT rules of my firewall. When I try to connect or use ftptest.net I get the following error
Status: Resolving address of 67.128.249.2
Status: Connecting to 67.128.249.2
Warning: The entered address does not resolve to an IPv6 address.
Status: Connected, waiting for welcome message...
Reply: 220-FileZilla Server 0.9.60 beta
Reply: 220-written by Tim Kosse (tim.kosse@filezilla-project.org)
Reply: 220 Please visit https://filezilla-project.org/
Command: CLNT https://ftptest.net on behalf of 216.138.9.233
Reply: 200 Don't care
Command: AUTH TLS
Reply: 234 Using authentication type TLS
Status: Performing TLS handshake...
Status: TLS handshake successful, verifying certificate...
Status: Received 1 certificates from server.
Status: cert[0]: subject='OU=Domain Control Validated,CN=moayerco.company' issuer='C=US,ST=Arizona,L=Scottsdale,O=GoDaddy.com\5c, Inc.,OU=http://certs.godaddy.com/repository/,CN=Go Daddy Secure Certificate Authority - G2'
Command: USER patronpoints
Reply: 331 Password required for patronpoints
Command: PASS *********
Reply: 230 Logged on
Command: SYST
Reply: 215 UNIX emulated by FileZilla
Command: FEAT
Reply: 211-Features:
Reply: MDTM
Reply: REST STREAM
Reply: SIZE
Reply: MLST type*;size*;modify*;
Reply: MLSD
Reply: AUTH SSL
Reply: AUTH TLS
Reply: PROT
Reply: PBSZ
Reply: UTF8
Reply: CLNT
Reply: MFMT
Reply: EPSV
Reply: EPRT
Reply: 211 End
Command: PBSZ 0
Reply: 200 PBSZ=0
Command: PROT P
Reply: 200 Protection level set to P
Command: PWD
Reply: 257 "/" is current directory.
Status: Current path is /
Command: TYPE I
Reply: 200 Type set to I
Command: PASV
Reply: 227 Entering Passive Mode (67,128,249,2,226,85)
Command: MLSD
Status: Data connection established, performing TLS handshake...
Error: TLS handshake failed: An unexpected TLS packet was received.
Any help is greatly appreciated.
errors after ISP change
Moderator: Project members
Re: errors after ISP change
Looks like some other program or network device is answering on that data connection port, it's not FileZilla Server.
-
- 500 Command not understood
- Posts: 2
- Joined: 2021-08-03 13:57
- First name: Jared
- Last name: Yargus
Re: errors after ISP change
I can't imagine what that would be. This server has been running for over 3 years now and nothing has changed aside from our public IP. I just went through and deleted and recreated the firewall and NAT rules for this thinking something might be hung up in the programming. no luck.