You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Nip-11 seems to be served on root domain, not on relay_url #381
From what I understand, the NIP-11 spec says the relay metadata should be served on the same URI that handles the WebSocket connection, not just the root domain. 
Right now it looks like Nostream always serves it at /, even when the relay is configured with a path like /v1, which feels inconsistent with that expectation.
Rough plan
First, trace how the NIP-11 response is currently wired up and where the HTTP handler is mounted
Then check how the relay_url path (like /v1) is handled for WebSocket upgrades
Update the routing so that:
-- Requests with Accept: application/nostr+json on the relay path return the NIP-11 document
-- Instead of defaulting everything to the root endpoint
Make sure this still works properly behind reverse proxies and doesn’t break existing setups
Goal
Have NIP-11 served on whatever path the relay actually lives on, so something like /v1 behaves correctly instead of only /.
If I’m misunderstanding how Nostream is intentionally handling this, happy to adjust before diving in.
@theAnuragMishra the issue isn’t even assigned, so there’s no reason to block others from picking it up.I’ve already looked into it and I’m wrapping up the changes. I’ll be opening a PR shortly.
If you’ve already done meaningful work, feel free to share it.
Activity
theAnuragMishra commentedon Apr 8, 2026
yeah should be available on
/v1.sagar-h007 commentedon Apr 8, 2026
@cameri I’d like to take this on.
From what I understand, the NIP-11 spec says the relay metadata should be served on the same URI that handles the WebSocket connection, not just the root domain. 
Right now it looks like Nostream always serves it at /, even when the relay is configured with a path like /v1, which feels inconsistent with that expectation.
Rough plan
-- Requests with Accept: application/nostr+json on the relay path return the NIP-11 document
-- Instead of defaulting everything to the root endpoint
Goal
Have NIP-11 served on whatever path the relay actually lives on, so something like /v1 behaves correctly instead of only /.
If I’m misunderstanding how Nostream is intentionally handling this, happy to adjust before diving in.
theAnuragMishra commentedon Apr 8, 2026
@sagar-h007 I have started my work on this. It would be better if you picked another one for your ai to plan out :)
sagar-h007 commentedon Apr 8, 2026
@theAnuragMishra the issue isn’t even assigned, so there’s no reason to block others from picking it up.I’ve already looked into it and I’m wrapping up the changes. I’ll be opening a PR shortly.
If you’ve already done meaningful work, feel free to share it.
cameri commentedon Apr 18, 2026
Thank you @sagar-h007 !