Something must have changed in the nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm back end recently, because all of my NWC connections silently stopped working.

I have my main profile running to my node to receive #zaps, and at some point over the last month, I discovered I was unable to use nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan or any other NWC connection.

Thanks to nostr:npub1q5sah9f3p9kl7uqdeaqskqwmg74ktxx70e0093dzh4lpzcp3t0mqzxky65 I was able to get it mostly working again by spinning up a separate account that’s not connected to my node, but for whatever reason, it still doesn’t work with nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955, so I’m relying on nostr:npub1wxl6njlcgygduct7jkgzrvyvd9fylj4pqvll6p32h59wyetm5fxqjchcan and manual zaps with nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 until I can figure out where the source of the problem lies.

Is anyone else having issues with NWC on nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955? #AskNostr