Hi, On Sat, Aug 31, 2019 at 05:34:22PM -0300, Antonio Terceiro wrote: > Can you give me a hint how can one reproduce this issue? what was > exactly the state of your proxy to cause this?
When performing the apt update, i had no cache setup on localhost. There was a cache configured on another machine on the network, but due to replacing the router port 3142 on my network gateway was not forwarded to the proxy. My setup was similar to someone setting up auto-apt-proxy on their machine without having an apt-cacher-ng (or other HTTP proxy) available or discoverable. I am therefore assuming this problem affects anyone running auto-apt-proxy outside of their usual network, like on a public hotspot. I am running network manager using my router's resolver. I don't think a misconfiguration on my side is responsible for this behavior. Thanks!
