Eugen

No other ideas, except of file/dirs permissions. Make sure those dirs/files (`%SystemRoot%\system32\drivers\etc`, `%SystemRoot%\system32\drivers\etc\hosts`, `C:/Users/trahloff/.vagrant.d/tmp/hosts.local`) are writable. Also what means `-a---`, "all" something? Did you try workarounds from the links you...

Sorry to hear that. The only thing I can help with, - will try to reproduce later with `Vagrant: 1.9.6` and `Vagrant-Hostmanager: 1.8.7` you mentioned before.

I tried with `Vagrant 1.9.1` and couldn't reproduce the issue. Hadn't any chance yet to try with `Vagrant 1.9.6`.

Thanks for detailed bug report and more investigation around this. Are you saying that your use case worked in py2 but failed in py3, you know where to fix and...

Your way of debugging and communicating this issue is technically solid! Thanks again for more details @jamesdreid and for reporting this bug.

Are you setting the hostname instead of full URL for your pip registry? Like `no_proxy=your-pip-repo,localhost,10.1.0.0/16`? Also make sure to use lower-case `no_proxy`.

Which config file do you mean? The envs needs to be placed for the respective services https://docs.stackstorm.com/packs.html#installing-packs-from-behind-a-proxy and then services should be restarted to pick that up. `st2actionrunner` is the...

Thanks for more info! I looked deeper in the history and this might be helpful to have more context when trying to find the fix these days: https://github.com/StackStorm/st2/pull/3556#discussion_r126786840 and https://github.com/pypa/pip/issues/2440

As pip doesn't have an explicit no_proxy setting and so we pass it via env variable, maybe try to debug further here: https://github.com/StackStorm/st2/blob/ce31176556be506606b83f6854630f8e6c0fd5ea/st2common/st2common/util/virtualenvs.py#L262-L266 and check if `env` indeed has no_proxy...

@donkopotamus Looks like you drilled down the problem really deep with the root-cause analysis. That's exactly the approach needed here. If you could open a PR with a bugfix and...