Custom Query (8117 matches)
Results (418 - 420 of 8117)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11936 | duplicate | Client timeout at "performing handshake" when using HTTP proxy | ||
| 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) |
|||
| #11934 | rejected | update.filezilla-project.org using self-signed certificate | ||
| Description |
Attempting to connect to update.filezilla-project.org is failing due to HSTS and the server using a self-signed certificate rather than a public CA or Let's Encrypt. |
|||
| #11932 | fixed | Priority not respected | ||
| Description |
When I change the priority of a file in the queue it is not recognized. As one file finishes the next file on the list is taken regardless of other files where the priority was set to "high" FileZilla Client Version: 3.42.1 Build information:
Linked against:
Operating system:
|
|||
