Page 1 of 3
No longer able to connect
Posted: 2021-02-12 17:58
by Seven
I don't know whether this is my host or FileZilla but I just upgraded to v3.52.2 and can no longer connect to any of my sites. Because it is all of them, my instant reaction is that it is probably a fault on the server but FileZilla gives the following "FATAL ERROR: Network Error: Software caused connection abort"
I'm getting exactly the same error for all my sites which normally have no issue connecting and like I said, it is only since FileZilla updated. I have a second PC and installed it on that but the same thing is happening.
Edit:
It's not my host. All my sites are still online and loading fast.
Re: No longer able to connect
Posted: 2021-02-14 04:33
by boco
Check if your firewall is blocking any FileZilla executable.
Re: No longer able to connect
Posted: 2021-02-14 10:19
by Seven
No, it's not that.
- connection_failure.png (154.89 KiB) Viewed 1819 times
Re: No longer able to connect
Posted: 2021-02-14 23:43
by boco
You are using SFTP, it seems. Is the fzsftp.exe application allowed to connect to SFTP servers (port 22)? Check the Comodo Application rules.
- comodo_fzsftp.jpg (67.32 KiB) Viewed 1803 times
Re: No longer able to connect
Posted: 2021-02-15 07:52
by Seven
Yes, it is set as an allowed application.
I have been using FileZilla for more than 20 years and it has always performed perfectly. It is just this latest version that will not connect. Is there some way I can get the installer for the previous version please?
Re: No longer able to connect
Posted: 2021-02-15 09:00
by botg
Nothing has changed in recent versions related to SFTP connection establishment, an old version would not do you any good.
Try re-making your firewall rules. When updating, the programs change, firewalls block changed programs.
Can you ping the target host?
Re: No longer able to connect
Posted: 2021-02-15 09:07
by Seven
Can you ping the target host?
Sorry for my lack of knowledge but what does that mean and how do you do it?
Re: No longer able to connect
Posted: 2021-02-15 09:08
by botg
Start cmd.exe and use the ping command.
Re: No longer able to connect
Posted: 2021-02-15 09:32
by Seven
- ping.png (76.66 KiB) Viewed 1784 times
Re: No longer able to connect
Posted: 2021-02-15 11:15
by boco
The ping is good, and it shows your ISP has IPv6 support (that's a good thing). Unfortunately, sometimes, using IPv6 still can give problems (as if they didn't have enough time to perfect it in the last ~20 years), especially if the ISP introduced it only recently.
Please try to use the direct IPv4 of that host to connect, by using 217.160.231.106 as Hostname (better even, use the IP you will get with the ping -4 u62402230.1and1-data.host command). Does connection work when IPv4 is used?
Re: No longer able to connect
Posted: 2021-02-15 12:05
by Seven
I don't know how to get it to use IPv4 because I can't find any such setting in the Site Manager.
That said, with all my sites, I still get "FATAL ERROR: Network Error: Software caused connection abort" but with 5 of them it finally connects after a second or third attempt. My 6th site was almost impossible to connect to however, after multiple retries it eventually connected. This one is not really a problem because I'm not using it anymore. Nonetheless, the fact that FZ was able to connect after several tries tends to suggest my host may be working on the server. The strange thing is that the sites themselves respond instantly. What do you think?
Re: No longer able to connect
Posted: 2021-02-15 22:16
by boco
I don't know how to get it to use IPv4 because I can't find any such setting in the Site Manager.
You just enter the IPv4 address in place of the Hostname you used before.
The strange thing is that the sites themselves respond instantly. What do you think?
Sites themselves run on web servers (serving HTTP(S)). FileZilla uses FTP or SFTP. All entirely different services with their own problems, each. Note that FTP SFTP and web servers do not even have to run on the same physical servers.
Re: No longer able to connect
Posted: 2021-02-16 07:45
by Seven
When I entered the IP address, as you suggested, it would not connect at all. I'm assuming that was the IPv4 address?
Re: No longer able to connect
Posted: 2021-02-16 12:55
by boco
Code: Select all
E:\>ping -4 u62402230.1and1-data.host
Pinging u62402230.1and1-data.host [217.160.231.106] with 32 bytes of data:
Reply from 217.160.231.106: bytes=32 time=37ms TTL=55
Reply from 217.160.231.106: bytes=32 time=30ms TTL=55
Reply from 217.160.231.106: bytes=32 time=27ms TTL=55
Reply from 217.160.231.106: bytes=32 time=28ms TTL=55
Ping statistics for 217.160.231.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 37ms, Average = 30ms
E:\>ping u62402230.1and1-data.host
Pinging u62402230.1and1-data.host [2001:8d8:1000:2f:4865:f2e1:d9e0:f82f] with 32 bytes of data:
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=40ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=31ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=30ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=31ms
Ping statistics for 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 40ms, Average = 33ms
E:\>
Test log, connection is good and fast:
Code: Select all
13:49:13 Status: Connecting to u62402230.1and1-data.host...
13:49:13 Response: fzSftp started, protocol_version=10
13:49:13 Command: open "anonymous@u62402230.1and1-data.host" 22
13:49:13 Trace: Looking up host "u62402230.1and1-data.host" for SSH connection
13:49:13 Trace: Connecting to 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f port 22
13:49:13 Trace: We claim version: SSH-2.0-FileZilla_3.53.0_beta1
13:49:13 Trace: Remote version: SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u1~ui10+2
13:49:13 Trace: Using SSH protocol version 2
13:49:13 Trace: Doing ECDH key exchange with curve Curve25519 and hash SHA-256 (unaccelerated)
13:49:13 Trace: Server also has ecdsa-sha2-nistp256/ssh-rsa host keys, but we don't know any of them
13:49:13 Trace: Host key fingerprint is:
13:49:13 Trace: ssh-ed25519 255 0d:15:61:04:10:c2:d7:ce:af:55:68:0a:7c:9c:b8:d7 1gx2w8Rtv3wCgi7Jh8myf/KVd72cRQbow03UP8P095Q=
13:49:16 Command: Trust new Hostkey: Once
13:49:16 Trace: Initialised AES-256 GCM outbound encryption
13:49:16 Trace: Initialised AES256 GCM outbound MAC algorithm (in ETM mode) (required by cipher)
13:49:16 Trace: Will enable zlib (RFC1950) compression after user authentication
13:49:16 Trace: Initialised AES-256 GCM inbound encryption
13:49:16 Trace: Initialised AES256 GCM inbound MAC algorithm (in ETM mode) (required by cipher)
13:49:16 Trace: Will enable zlib (RFC1950) decompression after user authentication
13:49:16 Status: Using username "anonymous".
13:49:16 Command: Pass: *********************
13:49:16 Trace: Sent password
13:49:18 Trace: Password authentication failed
Of course, authentication fails, in the end.
There seems to be a block on your side. Try the ping commands, do they resolve and work properly?
Re: No longer able to connect
Posted: 2021-02-16 16:44
by Seven
Code: Select all
C:\Windows\System32>ping u62402230.1and1-data.host
Pinging u62402230.1and1-data.host [2001:8d8:1000:2f:4865:f2e1:d9e0:f82f] with 32 bytes of data:
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=35ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=31ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=31ms
Reply from 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f: time=31ms
Ping statistics for 2001:8d8:1000:2f:4865:f2e1:d9e0:f82f:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 35ms, Average = 32ms
What was the second ping command you used?