Opened 6 years ago

Closed 6 years ago

#11805 closed Bug report (rejected)

Cannot Connect to Server or Uopdate Filezilla

Reported by: Steve McWilliam Owned by:
Priority: normal Component: FileZilla Client
Keywords: connect to server, update Cc: steve.mcwilliam@…
Component version: 3.39 Operating system type: Windows
Operating system version: Win-10 Pro, Ver.1803, Build 17134.441 on Intel Core2 Quad

Description

Dear Filezilla,

  1. Since the last but one update version of Filezilla I have been unable to connect to my FTP Host at 1&1; prior to this update all was working fine. I have checked my connection parameters and all are correct. I have also downloaded another FTP Client (CoreFTP LE) this morning and applied the same parameters and that is working fine connecting to my FTP Host without problems. The connection failure is shown below:

Status: Connecting to home163432264.1and1-data.host...
Response: fzSftp started, protocol_version=8
Command: open "u40428120@…" 22
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...
Status: Connecting to home163432264.1and1-data.host...
Response: fzSftp started, protocol_version=8
Command: open "u40428120@…" 22
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server

  1. Also, Filezilla fails on Checking for Updates with the message "Information about the latest version of Filezilla could not be retrieved. Please try again later.". My Internet connection is working fine in both Chrome and Firefox and also in Opera; and works fine with CoreFTP LE.

I urgently need Filezilla to upload changes to my websites. Anything you can suggest would be gratefully received. I have tried uninstalling Filezilla and reinstalling from scratch with a complete reset of parameters to no avail.

Cheers and thanks,
Steve J. McWilliam

Attachments (1)

filezilla.log (4.7 KB ) - added by Steve McWilliam 6 years ago.
Connect to Server Issue & Filezilla Update Error

Download all attachments as: .zip

Change History (5)

comment:1 by Steve McWilliam, 6 years ago

Operating system version: Win-10 Pro, Ver.1803, Build 17134.441Win-10 Pro, Ver.1803, Build 17134.441 on Intel Core2 Quad

by Steve McWilliam, 6 years ago

Attachment: filezilla.log added

Connect to Server Issue & Filezilla Update Error

comment:2 by Steve McWilliam, 6 years ago

Error report from Filezilla Update failure is given below:

Started update check on 2018-12-03 12:15:45
Own build type: official
Selected port usually in use by a different protocol.
CControlSocket::SendNextCommand()
CHttpConnectOpData::Send() in state 0
CControlSocket::ResetOperation(0)
CHttpConnectOpData::Reset(0) in state 0
CHttpControlSocket::FileTransfer()
Requesting https://update.filezilla-project.org/update.php?cpuid=sse%2Csse2%2Csse3%2Cssse3%2Csse4.1%2Clm&initial=1&manual=1&osarch=64&osversion=10.0&package=1&platform=x86_64-w64-mingw32&updated=0&version=3.39.0
CControlSocket::SendNextCommand()
CHttpFileTransferOpData::Send() in state 0
CHttpFileTransferOpData::Send() in state 1
CHttpFileTransferOpData::Send() in state 2
CHttpControlSocket::Request()
CHttpRequestOpData::Send() in state 17
CHttpRequestOpData::Send() in state 18
CHttpControlSocket::InternalConnect()
CHttpControlSocket::ResetSocket()
CHttpInternalConnectOpData::Send() in state 0
Resolving address of update.filezilla-project.org
Connecting to [2a01:4f8:171:1ce9::4]:443...
Connection timed out after 20 seconds of inactivity
CHttpControlSocket::ResetSocket()
CControlSocket::ResetOperation(2114)
CHttpInternalConnectOpData::Reset(2114) in state 0
CControlSocket::ResetOperation(2114)
CHttpRequestOpData::Reset(2114) in state 18
CHttpControlSocket::ResetSocket()
CControlSocket::ResetOperation(2114)
CHttpFileTransferOpData::Reset(2114) in state 3
File transfer failed

comment:3 by Bert, 6 years ago

I'm not a FileZilla team member, but since you didn't get a response in 7 days, here's a suggestion.

Try temporarily turning off your firewall, does it work then?

Regardless, ask your server administrator to open TCP_IN ports 30000:50000 in their firewall, and restart their firewall.
Then you retry.

If either solves your problem, please post a link to this thread here:
https://trac.filezilla-project.org/ticket/11809

comment:4 by Tim Kosse, 6 years ago

Resolution: rejected
Status: newclosed

A client-side firewall is blocking all network traffic from FileZilla.

Note: See TracTickets for help on using tickets.