chromium-browser ignores system proxy settings

Bug #1825983 reported by Thomas
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 18.04.2
chromium-browser 73.0.3683.86

Network proxy is configured via Settings GUI dialog. chromium-browser is started with verbose output:

[9810:9810:0423/134338.510775:VERBOSE1:proxy_config_service_linux.cc(484)] All gsettings tests OK. Will get proxy config from gsettings.
[9810:9810:0423/134338.510926:VERBOSE1:proxy_config_service_linux.cc(1243)] Obtained proxy settings from annotation hash code 11258689
[9810:9810:0423/134338.510949:VERBOSE1:pref_proxy_config_tracker_impl.cc(184)] 0x55e7b2944b00: set chrome proxy config service to 0x55e7b27e3f10

Listing all gsettings with proxy:
~$ gsettings list-recursively | grep proxy
will return:

org.gnome.system.proxy.http host 'gse.auk.cvclab.lan'
org.gnome.system.proxy.http port 9191
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.evolution.shell.network-config proxy-type 0
org.gnome.evolution.shell.network-config use-http-proxy false
org.gnome.system.proxy.https host ''
org.gnome.system.proxy.https port 0
org.gnome.system.proxy.socks host ''
org.gnome.system.proxy.socks port 0
org.gnome.system.proxy.ftp host ''
org.gnome.system.proxy.ftp port 0
org.gnome.system.proxy use-same-proxy true
org.gnome.system.proxy mode 'manual'
org.gnome.system.proxy autoconfig-url ''
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.0/8', '::1']
org.gnome.settings-daemon.plugins.screensaver-proxy active true
org.gnome.settings-daemon.plugins.screensaver-proxy priority 0

chromium-browsers fails to connect to the internet with the error message: ERR_CONNECTION_TIMED_OUT

Starting chromium-browser with the proxy command line parameter:
~$ chromium-browser --proxy-server="gse.auk.cvclab.lan:9191"
This starts the browser and the internet connection works fine.

With Firefox there are no issues, it works with the configured system proxy settings.

Regards

Tags: bionic
Revision history for this message
Thomas (teclab-at) wrote :
Revision history for this message
Olivier Tilloy (osomon) wrote :

Can you compare the output of the following page when chromium is launched with and without the --proxy-server command-line parameter?

    chrome://net-internals/#proxy

Revision history for this message
Thomas (teclab-at) wrote :

Doing what you say only shows two buttons: "Re-apply settings" and "Clear bad proxies". In both versions. There is nothing to compare.

What I did instead was using the net-internals events viewer.
The one which I started from command-line with a proxy shows the configured proxy.
The one which should use the system proxy shows "proxy_server":"DIRECT"

Revision history for this message
Thomas (teclab-at) wrote :

Here the log with command-line proxy

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Russ Dill (russ-dill) wrote :

In my case, it's ignoring a file:// based pac, which looks to be intentional:

https://bugs.chromium.org/p/chromium/issues/detail?id=839566#c7

Revision history for this message
Russ Dill (russ-dill) wrote :

This is also not working with a http:// url based pac, which should work.

Revision history for this message
Elizabeth (ms-lilibeth) wrote :

I experience the same issue on Ubuntu 20.04. Neither manual proxy settings, nor PAC file helps. Additionally, I've exported http_proxy and https_proxy environment variables wherever I could (.bashrc, .zshrc, /etc/environment)

I suppose, the fact that my PC is in the domain or that it has multiple admin users may play a role... but how?

I tried that hack with changing .desktop file
https://askubuntu.com/questions/513840/google-chrome-proxy-settings

But I found my executable in /snap/chromium/1528/bin/chromium.desktop and did not succeed to find the way to edit it (read-only file system). Moreover, this file will be rewritten during package update.

I am totally dissatisfied with the fact that I should run chromium via terminal or create some desktop shortcuts. Is there any hope that the issue will be fixed? What can I do for that?

P.S. I've tried Chromium 89.0.4389.90 - 91.0.4455.2, no one works.

Revision history for this message
Elizabeth (ms-lilibeth) wrote :

UPD: I have installed Google Chrome 89.0.4389.90 (Official Build), it works properly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.