My Start9 has Nostr RS Relay downloaded and running.
I have converted my npub to hex and whitelisted it.
Health checks are a green light.
Why can’t I use the ws://
.onion Nostr relay websocket URL in any Nostr clients?Doesn’t seem to matter what Nostr client I use. None of them connect to the relay.
What am I doing wrong?
#asknostr
Not so sure it’s you. Some I can’t while it works in others. I believe it’s dependent on client and device. Ex: Damus accepts ws:// while Primal does not, but I believe you may also have to have Orbot. Although it may not be client-side at all.
Were you able to successfully add it in Damus as a test?
Anyone want to weigh in on their experience @Start9 running Nostr Relay over Tor?
It connects on Damus but that’s been the only one. I don’t see it as a win getting it to connect there because Damus deleted zap functionality after Apple leaned on them.
More as a test so at least you know you’ve got it setup properly. Not sure if nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg has plans to accept Tor or not.
I'm pretty sure that relay should only be setup as a private relay to act as an archive of your personal npub activity + drafts. I've tried to use it for other stuffs but I think the NIPs it supports are limited.🤷
Start9 isn’t clearnet as of yet. So if running over tor it won’t work with NOSTR i believe…. Someone correct me if im wrong
if you're connecting to a web client over HTTPS, the browser won't allow plain WS:// websockets. you can work around this by self hosting a web client of your choice, I use noStrudel
