Summary
After configuring my self-hosted Nostr relay in all three sections (My Relays, Inbox Relays, Key Package Relays) in White Noise, the relay receives some connections but no MLS group events (kinds 443, 444, 445) are observed being published to it, even when creating fresh groups and sending messages. The relay infrastructure has been independently verified as functional.
Steps to reproduce
- Set up a self-hosted nostr-rs-relay accessible at a public wss:// URL with valid Let's Encrypt SSL
- Whitelist your pubkey on the relay
- In White Noise, navigate to Settings, Network Relays
- Add the relay to My Relays, Inbox Relays, AND Key Package Relays
- Force-close and reopen White Noise
- Create a brand new group (after the relay was added)
- Send several test messages
- Monitor the relay's logs
Expected behavior
MLS group events (kinds 443, 444, 445) should be published to the configured relay so it can serve as a backup or redundant relay for the group's encrypted content. At minimum, identifiable activity from White Noise should appear in the relay logs after sending messages.
Actual behavior
Relay logs show occasional connections with unspecified user-agents and long connection durations (likely White Noise), but no kind 443, 444, or 445 events are ever persisted. Events of kinds 10002 (NIP-65), 10050 (inbox relays), and 10051 (key package relays) appear from the same pubkey, but these may come from other Nostr clients sharing the same identity (Amethyst, noStrudel). I cannot definitively confirm any MLS group events are being attempted, let alone published.
Environment
App version: 2026.5.7 (Zapstore Android build)
OS/device: Google Pixel 8a, GrapheneOS
Additional context:
Relay infrastructure independently verified: direct WebSocket test (websocat wss://...) successfully connects, queries, and returns events.
SSL certificate valid (Let's Encrypt, issued by E7).
Relay configured to "Permit all Event Types" — kinds 443/444/445 are not filtered.
Pubkey is whitelisted on the relay.
Relay is publicly reachable at wss://relay..io via Start9's StartTunnel infrastructure (WireGuard reverse tunnel through VPS).
Same pubkey successfully publishes events to the same relay from Amethyst on GrapheneOS.
Group chat itself works correctly between two test devices using default public relays.
I cannot find any UI to configure group-level relay preferences. The Marmot protocol spec mentions the Group Data Extension carrying relay preferences inside the group state — is per-group relay configuration in the UI on the roadmap? Or should adding a relay in the three Network Relays sections automatically make it part of new groups' relay sets?
Happy to provide additional logs, run packet captures, or test specific diagnostic scenarios.
Summary
After configuring my self-hosted Nostr relay in all three sections (My Relays, Inbox Relays, Key Package Relays) in White Noise, the relay receives some connections but no MLS group events (kinds 443, 444, 445) are observed being published to it, even when creating fresh groups and sending messages. The relay infrastructure has been independently verified as functional.
Steps to reproduce
Expected behavior
MLS group events (kinds 443, 444, 445) should be published to the configured relay so it can serve as a backup or redundant relay for the group's encrypted content. At minimum, identifiable activity from White Noise should appear in the relay logs after sending messages.
Actual behavior
Relay logs show occasional connections with unspecified user-agents and long connection durations (likely White Noise), but no kind 443, 444, or 445 events are ever persisted. Events of kinds 10002 (NIP-65), 10050 (inbox relays), and 10051 (key package relays) appear from the same pubkey, but these may come from other Nostr clients sharing the same identity (Amethyst, noStrudel). I cannot definitively confirm any MLS group events are being attempted, let alone published.
Environment
App version: 2026.5.7 (Zapstore Android build)
OS/device: Google Pixel 8a, GrapheneOS
Additional context:
Relay infrastructure independently verified: direct WebSocket test (websocat wss://...) successfully connects, queries, and returns events.
SSL certificate valid (Let's Encrypt, issued by E7).
Relay configured to "Permit all Event Types" — kinds 443/444/445 are not filtered.
Pubkey is whitelisted on the relay.
Relay is publicly reachable at wss://relay..io via Start9's StartTunnel infrastructure (WireGuard reverse tunnel through VPS).
Same pubkey successfully publishes events to the same relay from Amethyst on GrapheneOS.
Group chat itself works correctly between two test devices using default public relays.
I cannot find any UI to configure group-level relay preferences. The Marmot protocol spec mentions the Group Data Extension carrying relay preferences inside the group state — is per-group relay configuration in the UI on the roadmap? Or should adding a relay in the three Network Relays sections automatically make it part of new groups' relay sets?
Happy to provide additional logs, run packet captures, or test specific diagnostic scenarios.