Plain Text Nostr

<-- back to main feed

thread · root 15d3b120…14c5 · depth 4 · · selected acce14a3…8f0e

thread

root 15d3b120…14c5 · depth 4 · · selected acce14a3…8f0e

Yusuf al-Texani -- 1d [parent] 
|    I copied the URL into Amber and the connection is all good on that end seemingly then I return to the webpage
|    and it says the connection was closed. i tried on both Vanadium and Brave browsers. Whenever the laptop lands,
|    I'll try the QR code method
|    reply [1 reply]
Yusuf al-Texani -- 1d
Same thing happens with nostrmedia, so it should be something going wrong with my GrapheneOS phone or Amber
reply [3 replies]
ethfi -- 1d [parent] 
|    When life gives lemons
|    reply
f527cf970ce2 -- 1d [parent] 
|    What relays are you using in Amber? wss://relay.nsec.app? or wss://relay.damus.io? Or Azzamos relay?
|    reply [1 reply]
f527cf970ce2 -- 1d [parent] 
     I can only guess, but the most common cause would be that the relay in the bunker:// token isn't reachable or
     isn't responding to kind 24133. Amber outputs the token with a relay=… parameter. If this relay is offline,
     slow, or has restrictive filters, you get exactly this error. You could try to regenerate the bunker token in
     Amber using a reliable NIP-46 relay like wss://relay.nsec.app.
     reply [2 replies]

Write a post

Sign in with a signing-capable method to publish.