Skip to content

Add fallback relay: relay.nostrocket.org is down, app loads no data - #73

Open
JeroenOnNostr wants to merge 1 commit into
nostrocket:masterfrom
JeroenOnNostr:fix/add-fallback-relay
Open

JeroenOnNostr wants to merge 1 commit into
nostrocket:masterfrom
JeroenOnNostr:fix/add-fallback-relay

Conversation

@JeroenOnNostr

Copy link
Copy Markdown

Problem

The app at https://nostrocket.github.io/oxygen/ currently loads no data at all — wss://relay.nostrocket.org, the only entry in defaultRelays, is no longer operational:

  • DNS still resolves to 45.77.143.197 and port 443 accepts TCP connections;
  • but the host now presents a TLS certificate for an unrelated domain (CN=abdeel.me), which additionally expired on 2026-01-11;
  • so every browser WebSocket connection fails during the TLS handshake and Oxygen never receives a single event.

It looks like the VPS behind relay.nostrocket.org was decommissioned or repurposed. (Issues are disabled on this repo, otherwise this diagnosis would be filed there.)

What changed

  • Adds wss://nostrocket.descendant.io to defaultRelays, alongside the existing wss://relay.nostrocket.org — the original is kept so everything just works again if it comes back online.
  • Points relayHint at nostrocket.descendant.io, since a hint pointing at a dead relay actively hurts event discovery. Happy to revert this line if you'd rather keep the old value.

The replacement relay

  • wss://nostrocket.descendant.io — public relay (open reads and writes, no auth) on Cloudflare Workers with auto-renewing TLS, so a certificate expiry can't kill it again.
  • Backfilled with all Nostrocket events still retrievable from public relays (relay.damus.io, relay.nostr.band, nos.lol, relay.primal.net, and others): problem events (1971/1972), consensus (2008/12008), rocket ignition (1031), identity tree (31009/1592), merit requests and votes (1602/1603), plus replies and deletes referencing the ignition event.
  • NIP-11 limits raised (max_limit / default limit 5000) so Oxygen's no-limit subscriptions get the full event set.

If you'd prefer to run this under a nostrocket.org domain, we're happy to hand the deployment over or add your relay alongside — and more generally, more than one entry in defaultRelays means a single dead relay can't take the whole app down again.

Test

  • npm install && npm run dev — the problem tracker renders the problem tree again, including the root problem d0afd68b5cafa58382edb38b7ac7feef229a916f22330922e4be6cd22193b1a5.
  • Relay check: curl -H "Accept: application/nostr+json" https://nostrocket.descendant.io returns the relay's NIP-11 document.

🤖 Generated with Claude Code

…t.org

relay.nostrocket.org is no longer operational (the host serves an
expired TLS certificate for an unrelated domain), and as the only
entry in defaultRelays its failure makes the app load nothing.

Add a community-run public relay, backfilled with the Nostrocket
event set recovered from public relays, and point relayHint at it.
The original relay stays in the list so it works again if revived.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant