nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxthwden5te0ve5kzar2v9nzumn0wd68yvfwvdhk6tcpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7qg6waehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd9uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qyfhwumn8ghj7un9d3shjtnxxaazu6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzqdxj75n57x2clnfvkfrrm2l2mhu2y8uy4njzg8dg3qprhuzueqy42q66z9I'm trying to connect with NWC from zeus v0.11.3 to my lnbits node. Zeus says "Error connecting to your node". The debug log in lnbits says:
2025-09-05 21:29:28.90 | INFO | New websocket connection at: '/api/v1/relay'
2025-09-05 21:29:28.91 | INFO | 185.195.236.83:0 - "WebSocket /nostrclient/api/v1/relay" [accepted]
2025-09-05 21:29:28.91 | INFO | connection open
2025-09-05 21:29:28.95 | INFO | New subscription: 'sub:1'
2025-09-05 21:29:29.26 | INFO | Closing subscription: 'SWVMA2reKjcKdn9mDKY2km'.
2025-09-05 21:29:29.26 | INFO |
Unsubscribe from 'SWVMA2reKjcKdn9mDKY2km'.
Original id: 'sub:1.'
It seems zeus unsubscribes, why is that? Can I get logs from zeus to see its side of the quarrel. Or do you have any other hints?
Login to reply
Replies (7)
Messed up the nostr:nprofile1qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3xamnwvaz7tmjv4kxz7fwvcmh5tnfduhszxnhwden5te0wdjkuerfwshxummnvekxzun99e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wghxcctwvshsz9nhwden5te0wfjkccte9ekk7um5wgh8qatz9uq3jamnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kz7qgnwaehxw309ahkvenrdpskjm3wwp6kytcprfmhxue69uhhqatjv9mxjerp9ehx7um5wghxcctwvshsz9mhwden5te0v96xcctn9ehx7um5wghxcctwvshsqgp56t6jwncetr7d9jeyv0dtatwl3gslsjkwgfqa4zyqywlstnyqj59uup0r handle. But here it is.
Which relay are you using? Might be better to use Alby’s instead of running your own.
Always could use the LNDHub interface or connect to LND directly if the box is web facing.
Ok, but is there a way to get logging from zaus?
I already run lndhub+zeus, but want to experiment with NWÇ.
Oh and NWC works fine from nostr:nprofile1qqs24yz8xftq8kkdf7q5yzf4v7tn2ek78v0zp2y427mj3sa7f34ggjcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcppemhxue69uhkummn9ekx7mp0qyg8wumn8ghj7mn0wd68ytnddakj703s8dt to the same LNbits server.
Nope. Not beyond the error log displayed on connection failure.
Ok thanks. Have you been running NWC from Zeus to LNbits successfully?
Not LNbits, but other services, yes.