Warning message about Tor

[takuma sato]

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.

This showed up after updating to Knots 29.2. Anyone knows what it means? Im using the same bitcoin.conf:

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

Everything seems to work fine. Im just paranoid that im leaking something or people can connect to my computer or node or something. The node is running on Debian. I want to be able to help the network but stay private and safe from people connecting into my stuff beyond serving the network. How do I harden this and why is this error going on anyway now if I did not change anything?

From what I've read, Tor does not work unless you use listen=1, so I set it like that
onlynet=onion guarantees I only interact with other Tor nodes and you don't leak your clearnet ip
discover=0 I don't remember but it's there
rpc and bind I remember reading back then you needed to put localhost there and not 0.0.0.0 for privacy reasons
proxy has the Tor port there, I think you required this create the onion service

I mean everything seems to be working. I get the onion cookie, my node shows up on bitnodes.io, so it should be good to go.

I just want to triple check im not screwing up with something here, last thing I want is people connecting to my computer or leaking something on a Tor context and now that warning has me confused so please let me know.

[nc50lc]

This showed up after updating to Knots 29.2. Anyone knows what it means? Im using the same bitcoin.conf:

It's one of the changes in this commit from Core that Knots also implemented.

Bitcoin Core PR link: github.com/bitcoin/bitcoin/pull/22729
Bitcoin Knots Release Notes link: github.com/bitcoinknots/bitcoin/blob/29.x-knots/doc/release-notes/release-notes-28.0.md

As the message suggests, you just need to add another config containing "=onion" after your bind setting like this: bind=127.0.0.1:8334=onion

-edit-
Fixed Knots release notes link

[DYING_S0UL]

This showed up after updating to Knots 29.2. Anyone knows what it means? Im using the same bitcoin.conf:

It's one of the changes in this commit from Core that Knots also implemented.

Bitcoin Core PR link: github.com/bitcoin/bitcoin/pull/22729
Bitcoin Knots Release Note link: github.com/bitcoinknots/bitcoin/blob/29.x-knots/doc/release-notes/release-notes-28.1.md

As the message suggests, you just need to add another config containing "=onion" after your bind setting like this: bind=127.0.0.1:8334=onion

Sorry for going a little off topic but what about this one? I got this a few days ago, and I forgot to post about it.

What exactly happened! I was running Bitcoin core, but had to close it, later that same day maybe after some hours when I reopened the the core, I got these two errors.

Is it because I did not closed core properly? Or were it running in the background? After a quick restart everything was back to normal.

[retaur]

Was tor still running and just Core wasn't? I think I usually reset this error by closing and reloading tor - it's likely the lock on the listening port is being held by the version that didn't close properly. But you can refresh that by restarting tor.

[Z390]

I would be worried too, next time I think it is better to ask before taking any steps? It could be too late already if something was supposed to happened.

Exposure at the exit node is real, traffic can leave the Tor network and becomes u encrypted and this will leave a room for malicious exit nodes to intercept unencrypted data,  before yoh know what's going on your personal details and sensitive data is gone.

[nc50lc]

-snip-

What exactly happened! I was running Bitcoin core, but had to close it, later that same day maybe after some hours when I reopened the the core, I got these two errors.

It's hard to give an accurate answer to this.
It could be the next reply that the "zombie process" is still using the port, but usually, it'll also lock the datadir which would've displayed a different error.

The best advice that i can give is to check your debug.log for relevant errors/warnings at the time of that incident.

[BlackHatCoiner]

Exposure at the exit node is real, traffic can leave the Tor network and becomes u encrypted and this will leave a room for malicious exit nodes to intercept unencrypted data,  before yoh know what's going on your personal details and sensitive data is gone.

This is not correct. There is no "exposure" to the exit node. When using listenonion=1 and onlynet=onion, you're not connecting to clearnet, and therefore, there is no Tor node to "exit" anything. When connecting to an onion address, you're fully encrypting everything transferred to the onion address' public key, so it's impossible for intermediary nodes of the network to decrypt it.

[...]

Is there any reason you're binding to 0.0.0.0? Did you just leave that value to not have any connection problems?

[DYING_S0UL]

[...]

Is there any reason you're binding to 0.0.0.0? Did you just leave that value to not have any connection problems?

I didn't do anything at all. Did not touched any setting, everything was on default.

I had to do a fresh installation of Bitcoin core a few months ago (the whole process of downloading and verifying), because I messed up somewhere while tweaking some setting. And while I was at it, I faced it. It was only a one time error, never encountered it a 2nd time, so I didn't paid much attention to it. Recently I got curious and asked about it in this thread.
 
My mistake, I did added one thing, maxuploadtarget, but nothing beyond that.