<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
<!-- Describe the issue -->
<!--- What behavior did you expect? -->
According to help menu:
-onion=ip:port Use separate SOCKS5 proxy to reach peers via Tor hidden services, set -noonion to disable (default: -proxy)
I would expect that if -proxy is set, but -onion is not, -proxy setting would be used for onion connections.
Instead, according to getnetworkinfo, the default Tor port (127.0.0.1:9050) is listed for onion, but ipv{4,6} both have the -proxy setting. I inspected the traffic and saw that indeed it is not honoring my -proxy setting.
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
Bitcoin Core Daemon version v0.17.0.1-9e87d82e7
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
OS: Qubes OS, Whonix 14 VM
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
