# How do I get add-apt-repository to work through a proxy?

I'm trying to follow the "Installing Cross Toolchain on Ubuntu 10.04 (Lucid) and 10.10 (Maverick) Hosts" instructions on wiki.linaro.org (on my Ubuntu 10.04 VM). The first step is:

sudo add-apt-repository ppa:linaro-maintainers/toolchain


But when I run that I get:

Error reading https://launchpad.net/api/1.0/~linaro-maintainers/+archive/toolchain: <urlopen error [Errno 110] Connection timed out>


I'm guessing the problem is with my configuration for my employer's proxy server, particularly for HTTPS.

When I opened https://launchpad.net/api/1.0/~linaro-maintainers/+archive/toolchain in Firefox, I got "The connection has timed out". I then went into Firefox Preferences -> Advanced -> Network -> Settings... and set HTTP Proxy to "gateway" and Port to 8080, and checked "Use this proxy server for all protocols". Then the page loaded. This supports my theory.

I've tried setting the http_proxy and https_proxy environment variables (both lower and upper case):

$set | grep -i proxy HTTPS_PROXY=https://gateway:8080 HTTP_PROXY=http://gateway:8080 http_proxy=http://gateway:8080 https_proxy=https://gateway:8080  I also tried changing them to: $ set | grep -i proxy
HTTPS_PROXY=gateway:8080
HTTP_PROXY=gateway:8080
http_proxy=gateway:8080
https_proxy=gateway:8080


And I tried adding this second line to /etc/apt/apt.conf:

Acquire::http::proxy "http://gateway:8080/";
Acquire::https::proxy "https://gateway:8080/";


But I continue to get the same error.

How do I troubleshoot this?

Update: I followed the instructions in the accepted answer to "Problem adding repositories and connecting from terminal behind a proxy" and got further:

$sudo add-apt-repository ppa:linaro-maintainers/toolchain Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 1DD749B890A6F66D050D985CF1FCBACA7BE1F97B gpg: requesting key 7BE1F97B from hkp server keyserver.ubuntu.com gpgkeys: HTTP fetch error 7: couldn't connect to host gpg: no valid OpenPGP data found. gpg: Total number processed: 0  I wonder if the "HTTP fetch error" means I also need to add "Defaults env_keep = http_proxy" to /etc/sudoers... Update #2: I added: Defaults env_keep="http_proxy" Defaults env_keep="https_proxy"  ...as in Comment 18 for bug 516032, but I still get the same "gpgkeys: HTTP fetch error 7: couldn't connect to host" error. And this is curious: $ sudo env | grep proxy
https_proxy=https://gateway:8080


...because http_proxy isn't there.

Update #3: Since the host of my VM is a laptop, I took it home and tried there (with no proxies):

\$ sudo add-apt-repository ppa:linaro-maintainers/toolchain
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 1DD749B890A6F66D050D985CF1FCBACA7BE1F97B
gpg: requesting key 7BE1F97B from hkp server keyserver.ubuntu.com
gpg: key 7BE1F97B: public key "Launchpad Linaro Overlay PPA" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)


It worked. So problem is related to proxy configuration. But I suppose I have a workaround.

-
Just for reference askubuntu.com/questions/60217/… –  Deepak Rajput Oct 14 '11 at 10:01

In addition to configuring proxies, tell sudo to consider the environment with the flag -E

export http_proxy=http://<proxy>:<port>
export https_proxy=http://<proxy>:<port>


export https_proxy=<username>:<password>@<proxy>:<port>

-
This worked for me! :) Thanks! –  RadiantHex Mar 1 '12 at 15:56
Ya really worked –  Shashwat Kumar Mar 16 '13 at 9:00
-E (after doing all of the other stuff above) got it working for me. –  cschooley May 24 '13 at 17:47
and yes, the https_proxy configuration was necessary... :P –  monkut Jun 14 '13 at 5:41

Use this:

sudo apt-key adv --keyserver-options http-proxy=http://URL:PORT/ --keyserver keyserver.ubuntu.com --recv-keys GPG_KEY


And replace uppercase letters accordingly.

It works for me!

Regards, Patxi

-
That's the definitive solution! THAANKS! –  linello Feb 28 '14 at 10:54
This does not actually "fix" add-apt-repository command execution. Indeed it works around one of its tasks. At least one additional command is necessary: sudoedit /etc/apt/sources.list.d/XXXX.list + manual edition to add the deb URLs... –  Chucky Dec 2 '14 at 11:24

Finally! You need to set https_proxy via:

export https_proxy=....


only set http_proxy is not enough.

And I needed to execute the add-apt-repository command as root, NOT via sudo.

Code:

sudo su

-

In /etc/apt/apt.conf.d/01proxy add something like this

Acquire::http { Proxy "http://192.168.0.99:3142"; };

This will proxy all aptitude downloads, but I think this is the only way to do this on the backend. If your proxy supports it, you can also use a url like http://my.proxy:port/www.target.site.com/url which I know works for apt-cache-ng

I'm not sure if add-apt-repository itsself uses these settings, but if you cannot make that work, you can always add the repository to your /etc/apt/sources.list or /etc/apt/sources.list.d/mytoolchain

Since 11.10 there is also a cross-toolchailable in the main repo, just apt-get install gcc-arm-linux-gnueabihf. There are also cross-toolchains available from emdebian, and some instructions here: http://gsoc.sitedethib.com/posts/apt-get_install_gcc-4.7-arm-linux-gnueabihf/

-
user72421: how did you know that proxy should be prefixed with 01 and not with another number? –  jgomo3 Sep 27 '13 at 23:22

system wide environment variables should really be added to:

/etc/environment

(use sudo/gksu)

but the error reported to you seems to state no gpg data was found so i would see if the proxy is somehow munging the output of encrypted traffic just a thought

so i would first open a 2nd term & run a continuous netstat to see if the connection to the proxy is in fact being made then check the proxy settings (if you have access) then if that does not give answers/cause last resort would be to tcpdump & inspect in wireshark

but as this is your employers proxy i would imagine it is pretty locked down & you aint gonna be able to get this kinda access so i'd say:

Get Back to WORK!

looooooool

or try a http tunnel ;)

-

Execute the below command in terminal

-

It seems that the proxy configuration is set up but somehow the server cannot be contacted...

I had a very similar issue which I resolved like this: The corporate proxy allows only port 80 and 443 for security reasons, so event when it is setup, since HKP protocol is using port 11371, it will not let you through.

So, short of SSH-ing out and getting the key from one of your servers outside, downloading it and installing it locally, you can specify the key server from on of the ones listed below and specify the port:

http://sks-keyservers.net/overview-of-pools.php

e.g.:

apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys XXXXX


Boom, Voila!

-

This helped me:

sudo https_proxy='https://user:password@proxyhost:port/' \


I guess that there are some environment variables which are not needed in the command but they do not harm.

-

The reason your sudoers change did not work as expected is that instead of:

    Defaults env_keep="http_proxy"
Defaults env_keep="https_proxy"


You should have written:

    Defaults env_keep+="http_proxy"
Defaults env_keep+="https_proxy"


Also make sure the space between Defaults and env_keep is a tab each time.

-