I'm able to terminate tls requests when I stand up a little python oneliner file server on the box, so I think I have the proxy well configured. I'm still seeing "error adding relay 'wss://
Discussion
...when using noscl to test the relay
turns out I was missing the appropriate directives to proxy websockets correctly. https://www.nginx.com/blog/websocket-nginx/ I was missing the proxy header and http version lines
Nice! Yeah, that's how I'm configured w/ nginx! Did you recommend your relay yet? I'll add it.
indeed I have: wss://nostr.drss.io
Got it
you can send a big clickable recommendation from the settings page.
thanks! it should be visible in your feed if you follow me, or from my profile page. I'm enjoying Relayer so far. now I'm wondering if I should just go all in and setup rsslay to get the pebblesDB backing instead of having to mess with postgres.
I'm also thinking about adding the reverse feature, syndicating nostr feeds into RSS.
rsslay is not a normal relay. the only thing it does is to produce nostr events from RSS feeds. it doesn't accept normal events.
better try https://github.com/atdixon/me.untethr.nostr-relay or https://sr.ht/~gheartsfield/nostr-rs-relay/, both use sqlite instead of postgres.
but if you like golang you can also use https://github.com/fiatjaf/relayer as a library, implement an interface and choose the datastore you want, even just memory or something else, I don't know, post all events to github or something like that.