I noticed o lot of zap receipt delivery failures on my server (see below).

Since zap requests may contain any relay, how to ensure that the receipts get delivered? 🤔

#asknostr

1) Access issues

wss://nostr.wine: msg: restricted: not an active paid member

wss://filter.nostr.wine/npub[...]=true: msg: auth-required: please authenticate before sending events

wss://lightningrelay.com: msg: blocked: pubkey not admitted

wss://relay.orangepill.dev: context deadline exceeded

2) Lookup issues

dial tcp: lookup relayer.fiatjaf.com on [local IP address]: no such host

dial tcp: lookup relay.current.fyi on [local IP address]: no such host

dial tcp: lookup nostr-2.zebedee.cloud on [local IP address]: no such host

dial tcp: lookup nostr.mutinywallet.com on [local IP address]: no such host

dial tcp: lookup nostr-relay.wlvs.space on 81.19.12.2:53: server misbehaving

3) HTTP errors

'wss://relay.plebstr.com': failed to dial: unexpected HTTP response status: 502

'wss://nostr.sethforprivacy.com': failed to dial: unexpected HTTP response status: 404

'wss://nostr.rocks': failed to dial: handshake error: bad HTTP protocol version

3) Certificate errors:

'wss://nostr-pub.semisol.dev': failed to dial: remote error: tls: internal error

'wss://nostr.onsats.org': failed to dial: tls: failed to verify certificate: x509: certificate is valid for onsats.org, not nostr.onsats.org

'wss://nostr.zebedee.cloud': failed to dial: tls: failed to verify certificate: x509: certificate is valid for names-hub.com, www.names-hub.com, not nostr.zebedee.cloud

'wss://nostr.plebchain.org': failed to dial: tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-10-29T12:34:48+01:00 is after 2024-05-07T23:00:42Z

4) Timeouts:

'wss://offchain.pub': failed to dial: dial tcp 142.171.216.28:443: i/o timeout

'wss://relay.nostriches.org': failed to dial: dial tcp 45.79.34.32:443: i/o timeout

Reply to this note

Please Login to reply.

Discussion

No replies yet.