0 sats \ 9 replies \ @k00b OP 14 Oct \ parent \ on: SN elects to go noncustodial on Nov. 5th - FAQ & AMA
We are working on better errors to diagnose these problems. Our Tor support is unreliable and I'm sorry.
write
preview
0 sats \ 8 replies \ @SwapMarket 14 Oct
Forcing users to open clearnet ports is dangerous and is similar to kyc (((
reply
0 sats \ 7 replies \ @k00b OP 14 Oct
Come on man. I'm not forcing you to do anything. I'm sorry Tor isn't working for you. I hope we can get it fixed soon.
reply
0 sats \ 6 replies \ @SimpleStacker 14 Oct
fwiw I'm getting the same error message, and I don't think I'm connected via Tor.
Currently just using Alby Hub Desktop.
reply
0 sats \ 5 replies \ @k00b OP 14 Oct
Are you using NWC? What kind of lightning node is Alby Hub connected to?
reply
0 sats \ 4 replies \ @SimpleStacker 14 Oct
Yes, NWC. I assume it's connected to the default lightning node that gets installed when you install the software.
With my Alby node I was already able to:
  1. Receive bitcoin into the wallet via blockchain.
  2. Connect to stacker.news LN node on LN.
  3. Route a payment to Bitrefill through stacker.news node.
  4. Attach the wallet via NWC. The green circle seems to indicate the wallet was attached successfully. However, when I set desired balance to 0 and click save, I get an error message saying "Failed to create test invoice: the public key does not have a wallet connected. (I guess it's not 100% same as the other user's error)
reply
0 sats \ 3 replies \ @k00b OP 14 Oct
That error suggests the NWC string might be invalid. Was this with a brand new NWC string?
reply
181 sats \ 2 replies \ @SimpleStacker 14 Oct
Yes, as far as I can tell.
I finally got it to work. As far as I can tell, I only got it to work if I check more than just "Create invoices" when creating the receive connection. I think I checked:
  • Create invoices
  • Read node info
  • Look up invoice status
  • Read transaction history
  • Read balance
Previously I only checked "Create invoices" and it would not work.
reply
17 sats \ 1 reply \ @k00b OP 14 Oct
I'm glad you got it working!
I think currently we expect read node info permissions which I'm not sure we need. @ek do you know why that's there?
view replies