yeah, LXD is very picky as for its TLS configuration. We only allow those ciphers because combined with TLS 1.2, we strongly believe they are the safest. Since we also run all the public image servers and the daemon, we don't need backward compatibility at all.
What's odd is that the exact same TLS configuration should be used when talking to images.linuxcontainers.org, so I'm unsure as to why your proxy would work for one and fail with the other. Unless it special cases port 443. images.linuxcontainers.org is contacted over port 8443, cloud-images.ubuntu.com is contacted over the usual HTTPs port (443). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575386 Title: Proxy issue with 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1575386/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
