Nostr Web Client

Woot! You might be the first person other than me that's using this image. I'll reconsider platform specific packages now with a little time off from work.

Galaxie 5000 9mo ago

Another question if you don’t mind. I’m now able to get some clients to connect to my Haven instance. When I post a note, the Portainer logs show that Haven fails to connect to three relays listed in the import file. I removed them from the import file, and restarted the stack/container, but it still tries to connect to them. How do I update things so it stops attempting to connect to those relays?

Reply to this note

Please Login to reply.

Discussion

sudocarlos 9mo ago

Its probably failing in the blastr list

Galaxie 5000 9mo ago

Ah ok, I didn’t check that. Seems obvious now that you mention it 😆

Galaxie 5000 9mo ago

I removed the three relays from the blastr file, did "Update the stack" and restarted the container, but Haven is still attempting to connect to two of the deleted relays:

2025/04/18 00:15:42 error connecting to relay failed to connect: error opening websocket to 'wss://relay.nostr.bg': failed to WebSocket dial: failed to send handshake request: Get "https://relay.nostr.bg": dial tcp: lookup relay.nostr.bg on 127.0.0.11:53: no such host

2025/04/18 00:15:57 error connecting to relay failed to connect: error opening websocket to 'wss://relay.siamstr.com': failed to WebSocket dial: failed to send handshake request: Get "https://relay.siamstr.com": connecting to the relay took too long

2025/04/18 00:16:02 🔫 blasted bde3d2e8817ab4894212b48c3196ca73adc22ec126f75d8ed5267ac4b7c4dc8a to 26 relays

Galaxie 5000 9mo ago

Nm didn’t actually delete the first time. All good.