Skip to content

Unable to resolve `localhost` with chutney

See onionmasq#133 (closed)

Currently, it does not seem to be possible to resolve localhost or other names provided in /etc/hosts when making a connection over chutney. I personally believe that /etc/hosts should be taken into account by exit nodes when running in a test environment, as name resolution is an important part of testing.

Steps to reproduce:
Have an arti proxy running on 127.0.0.1:9150 with chutney configured, and then

curl --socks5-hostname 127.0.0.1:9150 http://localhost

will give the following in the arti logs:

WARN arti::socks: connection exited with error: error: remote hostname lookup failure

I am not sure whether this is a chutney or a ctor issue. Feel free to point me to ctor in case I should open an issue there. 🙂

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information