Opened 10 years ago

Last modified 3 years ago

#4508 new Bug report

"Check For Updates" does not work when there is a HTTP proxy

Reported by: MiG Owned by:
Priority: normal Component: FileZilla Client
Keywords: automatic-application-update proxy Cc:
Component version: Operating system type: Windows
Operating system version: XP SP3

Description (last modified by Alexander Schuch)

If you use the online update function, it should use the global proxy settings.
atm there is no way using it when sitting behind a proxy.
Perhaps there sould be an option [in the update dialoge or in the global settings] to setup the behavior.

regards
Michael

Change History (8)

comment:1 Changed 10 years ago by Michael

I have attempted to enter proxy settings manually, but still cannot connect to the update server when behind a proxy. The same has been tested successfully when connecting directly to the Internet (no proxy). The configuration wizard is also unable to correct configure the necessary settings when behind a proxy.

OS: XP-SP3 & Win2008
FZ: 3.2.7.1

comment:2 Changed 10 years ago by LaNN

Hi,
Until the current FileZilla Client version 3.2.8.1, this bug still exist.
This is the result shown after the update failed:

Status: Disconnected from server
Status: Downloading /updatecheck.php?platform=i586-pc-mingw32msvc&version=3.2.8.1&osversion=5.1
Status: Resolving address of update.filezilla-project.org
Status: Connecting to 62.75.138.232:443...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out", trying next address.
Status: Connecting to 213.239.222.5:443...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out", trying next address.
Status: Connecting to [2a01:198:200:5b7::2]:443...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Disconnected from server: ETIMEDOUT - Connection attempt timed out
Error: Disconnected from server

I change the generic proxy settings and still produce the same result.

In my workplace, proxy server applied only to http. I can use ftp directly to internet. So my browser using proxy but my FileZilla client just leave generic proxy settings to none.

I think generic proxy settings is special for ftp proxy in this context.
I pretty sure the update check simply using http get to check for update.
So it seems your generic proxy settings not related to this.
You might need to set another http proxy settings or
just simply use the system proxy settings Eg. IE Internet Options in windows.
if still difficult, just use ftp to download a file that contain the latest version by operating system. If I can use ftp then I can also check for update.

Hope this words might help your team.

CallMeLaNN
23 Oct 2009

comment:3 Changed 10 years ago by Michael

The above still does not correct the problem in 3.2.8.1 or in 3.3.0 rc1. Error is as follows:

[[Image(Status: Disconnected from server
Status: Downloading /updatecheck.php?platform=i586-pc-mingw32msvc&version=3.3.0-rc1&osversion=5.1
Status: Resolving address of update.filezilla-project.org
Status: Connecting to 62.75.138.232:443...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out", trying next address.
Status: Connecting to 213.239.222.5:443...
Status: Connection attempt failed with "ETIMEDOUT - Connection attempt timed out".
Error: Disconnected from server: ETIMEDOUT - Connection attempt timed out
Error: Disconnected from server)]]

If Filezilla would just read the browser settings this would be much easier.

comment:4 Changed 7 years ago by Alexander Schuch

Summary: use global proxy settings for online update"Check For Updates" does not work when there is a HTTP proxy

comment:5 Changed 6 years ago by Alexander Schuch

Taken from #8678:

"I would prefer it if the Client used the same protocol to do the downloading than what it uses to do the checking.

i.e.: You're doing the check via HTTPS, so if that works, it should be safe to assume that the download also works via HTTPS.

This isn't the case right now, so while the Client tells me that there's a new update available, it can't download it, as it tries to do the download via HTTP, which requires authentication behind our proxy."

There are two problems:

1) FileZilla does not use global proxy settings.

2) FileZilla checks for a new version using HTTPS, but then tries to download the new version via HTTP.

comment:6 Changed 4 years ago by Alexander Schuch

Description: modified (diff)
Keywords: automatic-application-update added; update removed

comment:7 Changed 4 years ago by PrismAY

I just moved over to a new development VM in my work and it's in a domain that uses a proxy server. This issue still exists in the latest version as I can't check for updates any longer. Still fails even though I've entered the proxy server info and credentials in the settings. Info from Help | About below:

FileZilla Client


Version: 3.14.1

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-unknown-linux-gnu
Build date: 2015-10-16
Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1
Compiler flags: -g -O2 -Wall -g -std=gnu++14

Linked against:

wxWidgets: 3.0.3
GnuTLS: 3.4.4
SQLite: 3.8.11.1

Operating system:

Name: Windows Server 2012 R2 (build 9600), 64-bit edition
Version: 6.3
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq
Settings dir: C:\Users\xxxxxx\AppData\Roaming\FileZilla\

comment:8 Changed 3 years ago by Tolotos

Sad but true: That problem still exists with 3.25.1.

I've set both "FTP proxy" and "Generic proxy", and the proxy server is set in the system proxy settings, too.

I can access FTP sites well, but checking for an update fails every time.


FileZilla Client

Version: 3.25.1

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-unknown-linux-gnu
Build date: 2017-03-20
Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1
Compiler flags: -g -O2 -Wall -std=gnu++14

Linked against:

wxWidgets: 3.0.3
SQLite: 3.16.2
GnuTLS: 3.5.8

Operating system:

Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition
Version: 6.1
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx avx2 aes pclmulqdq rdrnd bmi2 bmi2

Note: See TracTickets for help on using tickets.