Does anybody have a problem of connecting wasabi wallet (v.2.6.0; standalone) with own full node (Bitcoin Core v28.1.0~2) through tor?
I’ve entered my onion address from RPC Interface section (without http:// prefix) but with :8332 postfix (also tried :8333).
I get “Bitcoin RPC is unresponsive” status in wasabi.
Also tried onion address from Peer Interface section. No luck.
For Bitcoin RPC credential string I used my RPC Username and RPC Password separated by colon without any quotes.
I’ve tested and confirmed the process with a couple of other wallets. It’s only Wasabi that does not work, either with the .local or .onion.
For .onion you’d use port 8332, for .local you’d use 443. Other than that, your description of what you’ve done is correct.
Thank you for sharing your experience! 
So we have to wait for the next release of wasabi and hope that it gets fixed, right?
Do you know if it has worked in prior versions of wasabi or is it just since the current release of wasabi?
We don’t have Wasabi in our integration guides despite it being fairly well known… and there must be a reason for that. I couldn’t connect to Bitcoin Core now, and I’d assume the lack of previous guides for Wasabi was because this has long been the case.
For the last few versions of macOS, there has been a new security feature where applications are blocked from accessing the local network. Wasabi does not appear in the list to assign permissions, which means it either isn’t currently set up to work properly, or it simply doesn’t even attempt to access the .local (if you use that – it to be honest, it seems to be configured by default to only access Core running on the same device).
Wasabi also has an option to run Tor inside the app, but that’s on another tab and seems rather specific to accessing this Wasabi API thing. Adding a .onion for Bitcoin Core doesn’t seem to work at all.
There’s a bug in the latest Wasabi version that connecting to a full node only works using an IP address. This is already fixed (see: fix: replace EndPoint.ToString() with 'ToEndpointString()'. by remcoros · Pull Request #13915 · WalletWasabi/WalletWasabi · GitHub), but has not been released yet.
Keep an eye out for the next version of Wasabi and then it should work with both a .local and .onion address.
Thank you very much for your reply and especially for your contribution to the wasabi project. Also I want to tell you that you do a great work by sharing your knowledge in this community. 
Never underestimate your share for the whole freedom tech movement! 
I’m trying to connect my Wasabi Wallet to my Bitcoin Core / Start9 node. Wasabi is asking for the Bitcoin RPC Endpoint and Bitcoin RPC Credential String. I tried asking MapleAI, but I can’t find anything that looks like “http://bitcoinrpc:password@127.0.0.1:8332” or “bitcoinrpc:password” either in the Start9 Server Info, Bitcoin Core or electrs. Any advice would be appreciated.
You certainly do have an RPC username and an RPC password very clearly provided in Bitcoin Core/Knots very clearly listed under Properties.
Thanks. Yes, found them. Also, discovered I was using an old version of Wasabi. The current version 2.7.1 works.