Hi there,
the bug tracker is not the right place for user support. APT does not
suddenly pick different proxies when running as a service. It does
respect your http_proxy and no_proxy variables. Please note that while
http_proxy does not override Acquire::http::proxy, no_proxy does. It
sounds likely that when you run update manually, you have your freight
server in the no_proxy variable.
You have plenty of options to configure this more reliably, such as
1) configure Acquire::http::proxy::archive.ubuntu.com to only proxy for
archive.ubuntu.com (repeat for all hosts you want proxy)
2) configure Acquire::http::proxy to your proxy and configuring
Acquire::http::proxy::freightserverhostname "DIRECT"
3) configure Acquire::http::proxy (or http_proxy) and set no_proxy in
/etc/environment(.d)
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055717
Title:
Acquire::http::proxy ignored / used inconsistently?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2055717/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
