Custom Query (7886 matches)
Results (190 - 192 of 7886)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#11937 | worksforme | Can't install latest version 3.41.2 | ||
Description |
I'm on version 3.41.2. I can't report a bug without upgrading to 3.42.1. When I upgrade it wants me to load 3rd party virus protection software. My company doesn't allow that, so I cancel out of it and it doesn't install the software. So I can't report the bug. Which is by the way, Filezila runs at system startup and I don't want it to. And I can't find it in the startup files. My only option at this point is to uninstall it, and install it when I want to run it. Pretty lame stuff. Thanks, Peter |
|||
#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. |