Nostr Web Client

Never seen this before. Any help #asknostr?

Perhaps it is an nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 issue at the moment. Anyone else having issues?

nostr:nevent1qqsvwdhk98f9yssjxlwyxkgharp644ucynt4tzdwja7dceeg89dwewgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqsrggjezku9e57qqp3znl3c8fkkl7dupkcf4redrjen42cwgdsmupsgqqqqqqs3ee5np

Reply to this note

Please Login to reply.

Discussion

John Dee 11mo ago

Working here with my own alby hub.

PermaNerd 🌱 💻 11mo ago

Cheers

DeAllen Young 11mo ago

Yeah, this happens. Check to see if your node is signed into Alby. The connection will log out your node whenever they are doing system updates, or something like that. I've had this happen to me a few times.

PermaNerd 🌱 💻 11mo ago

Apparently it fixed itself. I can now zap. Cheers