Comment 3 for bug 2025978

I've tested with these additional juju model-config settings. Please confirm if you have these ones set as well, meaning apt-http-proxy, apt-https-proxy. My local proxy is at 10.76.244.153:8080 and I can confirm traffic crossing the proxy:

apt-ftp-proxy model http://10.76.244.153:8080/
apt-http-proxy model http://10.76.244.153:8080/
apt-https-proxy model http://10.76.244.153:8080/
apt-mirror default ""
apt-no-proxy default ""
ftp-proxy model http://10.76.244.153:8080/
http-proxy model http://10.76.244.153:8080/
https-proxy model http://10.76.244.153:8080/
no-proxy default 127.0.0.1,localhost,::1

Sample of traffic logs from proxy during juju deploy:

10.76.244.203 - - [06/Jul/2023:21:08:37 +0000] "CONNECT api.launchpad.net:443 HTTP/1.1" 200 215160 "-" "-"
10.76.244.203 - - [06/Jul/2023:21:08:45 +0000] "GET http://archive.ubuntu.com/ubuntu/pool/main/l/language-pack-en-base/language-pack-en-base_22.04%2b20230209_all.deb HTTP/1.1" 200 438391 "-" "Debian APT-HTTP/1.3 (2.4.9) non-interactive"

Of course, this is just testing with a proxy, not in a DMZ.

Installation succeeds and the landscape-server application reaches the status "Waiting on relations"