Opened 4 months ago

Closed 4 months ago

#11936 closed Bug report (duplicate)

Client timeout at "performing handshake" when using HTTP proxy

Reported by: Fr3dY Owned by:
Priority: normal Component: FileZilla Client
Keywords: http proxy, handshake Cc:
Component version: 3.42.1 Operating system type: Windows
Operating system version: Windows 7 Enterprise

Description

Client is unable to connect via HTTP proxy, it gets stuck at "performing handshake".
I've been able to do it using the same proxy on earlier FileZilla client versions (WinSCP is working too).

Here are the debug messages:

Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection timed out after 60 seconds of inactivity
Error:	Could not connect to server
Status:	Waiting to retry...
Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection timed out after 60 seconds of inactivity
Error:	Could not connect to server
Status:	Disconnected from server
Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection attempt interrupted by user
Status:	Disconnected from server
Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection attempt interrupted by user
Status:	Disconnected from server
Trace:	CRealControlSocket::DoClose(66)
Trace:	CControlSocket::DoClose(66)
Trace:	CRealControlSocket::DoClose(66)
Trace:	CControlSocket::DoClose(66)
Trace:	CControlSocket::DoClose(66)
Trace:	CFileZillaEnginePrivate::ResetOperation(0)
Trace:	CControlSocket::SendNextCommand()
Trace:	CFtpLogonOpData::Send() in state 0
Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection timed out after 60 seconds of inactivity
Trace:	CRealControlSocket::DoClose(2050)
Trace:	CControlSocket::DoClose(2050)
Trace:	CFtpControlSocket::ResetOperation(2114)
Trace:	CControlSocket::ResetOperation(2114)
Trace:	CFtpLogonOpData::Reset(2114) in state 1
Error:	Could not connect to server
Trace:	CFileZillaEnginePrivate::ResetOperation(2114)
Status:	Waiting to retry...
Trace:	CRealControlSocket::DoClose(66)
Trace:	CControlSocket::DoClose(66)
Trace:	CControlSocket::DoClose(66)
Trace:	CControlSocket::SendNextCommand()
Trace:	CFtpLogonOpData::Send() in state 0
Status:	Connecting to <<ftp_server>> through HTTP proxy
Status:	Resolving address of <<proxy_dns>>
Status:	Connecting to <<proxy_ip:port>>...
Status:	Connection with proxy established, performing handshake...
Error:	Connection timed out after 60 seconds of inactivity
Trace:	CRealControlSocket::DoClose(2050)
Trace:	CControlSocket::DoClose(2050)
Trace:	CFtpControlSocket::ResetOperation(2114)
Trace:	CControlSocket::ResetOperation(2114)
Trace:	CFtpLogonOpData::Reset(2114) in state 1
Error:	Could not connect to server
Trace:	CFileZillaEnginePrivate::ResetOperation(2114)

Change History (2)

comment:1 Changed 4 months ago by Fr3dY

Might be related to #11915 - Proxy connect timeout?

comment:2 Changed 4 months ago by Tim Kosse

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.