Error message after Tor update

7 replies 411 views
alpha23Member
Posts: 31 · Reputation: 79
#1Jun 20, 2025, 01:36 AM
I just updated to Knots 29.2 and now I’m getting this weird warning. I’m on Debian and my bitcoin.conf hasn’t changed. Everything seems fine, but I’m worried about leaking my info or someone connecting to my node. How can I secure this? Also, why am I seeing this message suddenly?
3 Reply Quote Share
0xChadNewbie
Posts: 138 · Reputation: 3
#2Jun 20, 2025, 03:51 AM
That’s related to a change in the Core version that Knots adopted. You need to tweak your config a bit. Just add =onion after your bind setting like this: bind=127.0.0.1:8334=onion. Should fix your issue.
6 Reply Quote Share
Posts: 10 · Reputation: 19
#3Jun 20, 2025, 06:25 AM
Off topic, but I had a different error with Core a few days ago. Closed it down, then later opened it and got some weird errors. Could it be because I didn’t shut it down properly? Restarting fixed it, but still...
1 Reply Quote Share
SwiftNovaNewbie
Posts: 23 · Reputation: 14
#4Jun 22, 2025, 06:42 AM
Was Tor still running when you closed Core? I usually solve this by just restarting Tor. Sometimes it locks the port when it doesn’t shut down right.
0 Reply Quote Share
roguebossNewbie
Posts: 9 · Reputation: 18
#5Jun 22, 2025, 11:22 AM
Honestly, I’d be paranoid too. Next time you might wanna double-check before making changes. If there’s a breach, it could already be too late to fix it. Exit node vulnerabilities are a real concern.
4 Reply Quote Share
0xChadNewbie
Posts: 138 · Reputation: 3
#6Jun 22, 2025, 02:15 PM
Tough to say for sure. Could be that zombie process holding the port. But usually, if that happens, you'd see a different error related to the data directory.
1 Reply Quote Share
dave.forkMember
Posts: 143 · Reputation: 185
#7Jun 22, 2025, 05:00 PM
That’s not how it works. If you’ve got listenonion=1 and onlynet=onion, you’re safe. No connecting to clearnet means no exit node exposure. Just encrypting everything to the onion address.
4 Reply Quote Share
Posts: 10 · Reputation: 19
#8Jun 22, 2025, 08:55 PM
I didn’t change anything major. Just followed the defaults. Had to reinstall Core before, messed something up then. It was a one-off error, didn’t think much of it until now. Oh, I did change maxuploadtarget, but that's it.
3 Reply Quote Share

Related topics