It's not just from the localhost. Apt-proxy is crashing if it is access by a VM running on the machine that is running apt-proxy.
Example:
Machine xxx.xxx.xxx.249 is running VMWare Server, with bridged networking
Machine xxx.xxx.xxx.247 is a virtual machine running on the above machine, with its network connection being bridged out over the same interface that hosts .249.
When it tries to access the apt-proxy instance on .249, apt-proxy crashes with the above traceback. Most odd.
Is this a VMWare bug of some kind? But network bridging is supposed to be transparent to a VM.
Additional information:
It's not just from the localhost. Apt-proxy is crashing if it is access by a VM running on the machine that is running apt-proxy.
Example:
Machine xxx.xxx.xxx.249 is running VMWare Server, with bridged networking
Machine xxx.xxx.xxx.247 is a virtual machine running on the above machine, with its network connection being bridged out over the same interface that hosts .249.
When it tries to access the apt-proxy instance on .249, apt-proxy crashes with the above traceback. Most odd.
Is this a VMWare bug of some kind? But network bridging is supposed to be transparent to a VM.
Any ideas?