Closed gpanders closed 5 years ago
Looks like your company's Squid hijacks the port which anaconda-mode has been trying to use. I think the only solution for this is either do something so the proxy doesn't do this anymore, or to improve anaconda-mode so it accepts valid ports which it should use.
You can change anaconda-mode-localhost-address
to a different port that is free behind your proxy.
I think this is now solved by making sure localhost
is not intercepted by my proxy (by adding it to the no_proxy
environment variable and the Network Preferences in macOS).
So I know this issue has been brought up before. But my problem doesn't seem to match what others are experiencing.
I work behind a corporate proxy. When I'm not connected to my work network everything works fine, but as soon as I connect to my VPN things go bunk.
Here is my
init.el
:I have tried with and without setting
anaconda-mode-localhost-address
.Below is the
*anaconda-response*
log. It is reporting that it could not connect to 127.0.0.1:62839; however,lsof -nPi4:62839
shows that the port is LISTENING.I noticed the presence of a Squid server. I don't have one installed as far as I know. Is that part of anaconda-mode? If not, then I suspect it is part of my company's proxy toolchain.
*anaconda-response*
: