Replying to Avatar ⚡GhostBTC⚡

Yes I put damus.io in there. I also put my npub in the whitelist section
Avatar
Yonle 1y ago

If you are connecting to local network, Ensure that you are connecting with ws:// and NOT wss://.

Reply to this note

Please Login to reply.

Discussion

33
unknown 1y ago

Why is that ?

Avatar
Yonle 1y ago

wss:// is for secured connection. Non secured connection should use ws:// instead. If you have a working TLS, You could use wss://. But for your setup that only serves locally, there's no need for TLS.

33
unknown 1y ago

Oh ty. I never seen ws/wss until Nostr came along.

Avatar
Yonle 1y ago

Nostr relays are using websocket to communicate with relays. So you will see ws:// or wss:// at the end of nostr relays URL.

Websockets are not nostr specific thing. It's an internet thing.

Avatar
⚡GhostBTC⚡ 1y ago

Yeah I did that. When I start bostr it says listening on ws://0.0.0.0:8080 and connected to wss://relay.damus.io. Do I put ws://0.0.0.0:8080 in my nostr client relay section? Should it work after that? (It didnt) The only thing I changed in the config is the damus relay. Is there anything else Im missing that is required?

33
unknown 1y ago

You can connect locally on your network by adding ws://server-ip:8080

Otherwise you need nginx reverse proxy with ssl so you can access it anywhere

wss://domain

Avatar
⚡GhostBTC⚡ 1y ago

ws://server-ip:8080 doesnt work. Nothing loads :(