Bitcoin Forum
November 18, 2025, 09:41:28 PM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Warning message about Tor  (Read 102 times)
takuma sato (OP)
Hero Member
*****
Offline Offline

Activity: 813
Merit: 702


View Profile
November 14, 2025, 04:51:43 AM
Merited by ABCbits (2)
 #1

Quote
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:


Quote
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
Legendary
*
Offline Offline

Activity: 2968
Merit: 7975


Self-proclaimed Genius


View Profile
November 15, 2025, 03:49:16 AM
Last edit: November 17, 2025, 05:04:58 AM by nc50lc
Merited by ABCbits (4), bitmover (2)
 #2

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
Hero Member
*****
Offline Offline

Activity: 854
Merit: 866


The Alliance Of Bitcointalk Translators - ENG>BAN


View Profile WWW
November 16, 2025, 09:32:46 PM
 #3

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.


.
 betpanda.io 
 
ANONYMOUS & INSTANT
.......ONLINE CASINO.......
▄███████████████████████▄
█████████████████████████
█████████████████████████
████████▀▀▀▀▀▀███████████
████▀▀▀█░▀▀░░░░░░▄███████
████░▄▄█▄▄▀█▄░░░█▄░▄█████
████▀██▀░▄█▀░░░█▀░░██████
██████░░▄▀░░░░▐░░░▐█▄████
██████▄▄█░▀▀░░░█▄▄▄██████
█████████████████████████
█████████████████████████
█████████████████████████
▀███████████████████████▀
▄███████████████████████▄
█████████████████████████
██████████▀░░░▀██████████
█████████░░░░░░░█████████
███████░░░░░░░░░███████
████████░░░░░░░░░████████
█████████▄░░░░░▄█████████
███████▀▀▀█▄▄▄█▀▀▀███████
██████░░░░▄░▄░▄░░░░██████
██████░░░░█▀█▀█░░░░██████
██████░░░░░░░░░░░░░██████
█████████████████████████
▀███████████████████████▀
▄███████████████████████▄
█████████████████████████
██████████▀▀▀▀▀▀█████████
███████▀▀░░░░░░░░░███████
██████░░░░░░░░░░░░▀█████
██████░░░░░░░░░░░░░░▀████
██████▄░░░░░░▄▄░░░░░░████
████▀▀▀▀▀░░░█░░█░░░░░████
████░▀░▀░░░░░▀▀░░░░░█████
████░▀░▀▄░░░░░░▄▄▄▄██████
█████░▀░█████████████████
█████████████████████████
▀███████████████████████▀
.
SLOT GAMES
....SPORTS....
LIVE CASINO
▄░░▄█▄░░▄
▀█▀░▄▀▄░▀█▀
▄▄▄▄▄▄▄▄▄▄▄   
█████████████
█░░░░░░░░░░░█
█████████████

▄▀▄██▀▄▄▄▄▄███▄▀▄
▄▀▄█████▄██▄▀▄
▄▀▄▐▐▌▐▐▌▄▀▄
▄▀▄█▀██▀█▄▀▄
▄▀▄█████▀▄████▄▀▄
▀▄▀▄▀█████▀▄▀▄▀
▀▀▀▄█▀█▄▀▄▀▀

Regional Sponsor of the
Argentina National Team
retaur
Jr. Member
*
Offline Offline

Activity: 56
Merit: 12


View Profile
November 16, 2025, 11:05:11 PM
 #4

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
Sr. Member
****
Offline Offline

Activity: 1246
Merit: 355


Contact @yahoo62278 on telegram for marketing


View Profile
Today at 05:03:19 PM
 #5

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.


Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!