After updating to latest Knots there is a warning about Tor

General
1

I updated to the latest 29.2 version and I this warning window showed up:

Warning: You are using a common listening port (127.0.0.1:8333) for both Tor and local connections. All connections to this port will be assumed to be Tor connections, and will be denied any whitelist permissions. If this is not your intent, setup a separate -bind=[:]=onion configuration, or set -listenonion=0.

What does this mean? I did not change anything on bitcoin.conf

Settings are:

rpcbind=127.0.0.1
bind=127.0.0.1
proxy=127.0.0.1:9050
server=1
listen=1
listenonion=1
onlynet=onion
discover=0

What is going on with that? Things seem to be working fine. I get 10 peers and my onion is available. Just not sure what that warning is about.

I want to have privacy, not have random people connecting to my computer obviously, but I want to help the network, so im not sure if these are the correcting settings.

I rarely use RPC commands, I only use the command line within the GUI. I think I used it once to do some of the stuff I did when porting the old wallet file into the new one.

In bitnodes io I checked and it shows up green but it says:

" * #### PENDING

Node status pending activation"

Not sure about that.

2

If I’m interpreting the warning correctly, it is saying that bitcoin is listening locally on 127.0.0.1:8333 and that Tor is configured to forward traffic on the tor port also to 127.0.0.1:8333. So to play it safe, bitcoin will treat all traffic as if they are tor connections (which have a bit more restrictions IIRC, such as whitelisted, where you would not want all Tor peers to be treated as trusted local peers). This is actually what you want it to do in this scenario, so you can probably ignore the message.

But if you want to test that theory, you could dis-ambiguate them in your config. I’m not sure on the exact syntax, but maybe something like this for your “bind” param:

bind=127.0.0.1:8334=onion

I’m not sure on the bitnodes question. I do know that this state typically happens when a new node has just been seen (bitnodes waits for another scan to discover it again before it considers it an active node). In your case, though, you have been running for a while so I’m not sure why it is still seeing that. Have you been ofline for a long time, or changed anything in your Tor configuration or something that might have changed your .onion address?