Proxy settings not applied system-wide, are not used by Software Update or apt

Bug #1730672 reported by John
92
This bug affects 19 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Low
Unassigned
update-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The Network Proxy settings available under Settings/Network are not applied system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a proxy here:
- does not modify /etc/environment
- does not set root's http_proxy, https_proxy, ftp_proxy environment variables

This means that apt and Software Updates do not receive the proxy settings, and package checks/updates/installs fail.

workaround:

sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update

etc

Tags: bot-comment
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1730672/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
John (john-e-francis) wrote :

re-direct to gnome-shell.

affects: ubuntu → gnome-shell (Ubuntu)
affects: gnome-shell (Ubuntu) → gnome-control-center (Ubuntu)
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
Thorsten Greeb (thorsten-greeb) wrote :

Importance: Low? Are you sure?

In environments where Internet access is only possible via proxy

- Ubuntu Software: Not working
- Software Updater: Not working
- Automatic install of security updates: Not working
- Install Languages (Language Support): Not working
- ...

I find this quite critical!

Revision history for this message
John (john-e-francis) wrote :

Thorsten - you can workaround a few different ways. For me, it's a pain because I move from a proxy-only to a non-proxy environment as I move my workstation around.

Workarounds:
1. set the http_proxy, https_proxy, ftp_proxy environment variables in root's environment, reboot.

2. prefix any apt command with the variables,ie

sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update
sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt upgrade
sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt install [package]

Hope that helps. Proxy issues have been appearing on and off in Ubuntu for a long time (9.x). They usually get sorted out eventually.

etc

Revision history for this message
David Biró (fxdave) wrote :

Same in here, it is an annoying feature. How can I contribute and fix this if no one does?

Revision history for this message
Jason Heeris (detly) wrote :

I just upgraded from 17.04, but it's impossible to complete the upgrade because of this.

Revision history for this message
Anushka Trivedi (opheliagame) wrote :

I was able to make apt work, by manually editing the /etc/apt/apt.conf file, and removing the proxy information from there. But I am having trouble installing any snaps, and still have to find a way to make that work.

Jason, I upgraded from 17.04 as well but I did not have any trouble interestingly. I think I removed the system wide proxy in 17.04 before upgrading, because that certain university proxy won't let me grab the upgrade, but then while I am using 17.10 the env variables($http_proxy, etc) are set to that proxy, for some reason. I have not used the proxy since upgrading or during the upgrade.

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

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

Changed in update-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Sanjana Sunil (trial) wrote :

Can the priority level be changed to something higher? This is a pretty important issue.

Revision history for this message
amer (aqua2) wrote :

this bug affects my advisor's university desktop ... i updated it to 18.04 , it was working 16.04

Revision history for this message
amer (aqua2) wrote :

by the way i used offline ISO for installing a fresh 18.04 .

Revision history for this message
daniel (danielturgeon) wrote :

I installed a fresh copy of 18.04 from an iso too and the issue is still persisting, the proxy issue is preventing us to deploy an important machine for our organization will there be a fix for this issue soon?

Revision history for this message
Sebastien Bacher (seb128) wrote :

@daniel, could you give some specifics on your issue you are having. Can't your organisation manually modif the apt configuration or environement variable? do you rely on the GNOME tool to apply manually the configuration on each machine, or how does it work?

Revision history for this message
daniel (danielturgeon) wrote :

@seb128, here are some details. We don't rely on the GNOME tool. We only have one machine and I manually added it to out Windows AD domain. Applying the changes to the apt.conf and environment variable works but it necessitates to insert a username a password, correct me if I'm wrong, which I find a bit counter intuitive security wise. is there a way to modified it so prompts the users for their password.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Using the graphical tool would also prompt you for a password to be able to apply the change to the system so it wouldn't make a difference for you?

Revision history for this message
Arthur Picht (picht) wrote :

I can confirm that bug for a fresh installed 18.04 working behind a corporal http/https-proxy that requires authentication.

Although configuring Settings/Network, environment config file, apt and all gsettings under org.gnome.system.proxy including authentication correctly, Ubuntu-Software-GUI displays the following error message when trying to update: “… failed to download https://extensions.gnome.org//static/extensions.json: Proxy Authentication Required” and “… failed to download https://cdn.fwupd.org/downloads/firmware.xml.gz.asc: Proxy Authentication Required”

Yes, I can work around it by using apt on command line.

But: Apparently Ubuntu-Software, the key tool for maintaining system security, does not work behind an authenticated proxy. Should that not be reason enough to value the bug higher than low?

Revision history for this message
Dark Knight (trungnth) wrote :

Important: Low? What a joke! My computer connected to the university network via proxy, because of this bug I can not install anything from Software Center. Please fix this bug.

You can manual fix this bug by using this script https://github.com/nityanandagohain/proxy_configuration

Revision history for this message
rajiv jain (rajiv13jain) wrote :

On my 18.04 i have copied the content of proxy.conf to apt.conf and it worked

sudo cp /etc/apt/apt.conf.d/proxy.conf /etc/apt/apt.conf

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.