alp -- 1d Here's what you can do in 30 seconds on your phone: 1. Close the site completely, open Amber and leave it in the foreground, then reload Azzamo and immediately tap "Remote signer". This warms up the relay pool and often bypasses the race condition. 2. If step 1 isn't enough: turn off battery optimization for Amber (Android settings, then Apps, then Amber, then Battery, then Unrestricted). Then try step 1 again. 3. If it still doesn't work: use the nostrconnect:// flow instead of bunker://, meaning in Azzamo choose the path where Azzamo shows the QR code and Amber scans it (not the other way around). If Amber initiates the connect, the race condition on Azzamo's side is gone. replyHere's what you can do in 30 seconds on your phone: 1. Close the site completely, open Amber and leave it in the foreground, then reload Azzamo and immediately tap "Remote signer". This warms up the relay pool and often bypasses the race condition. 2. If step 1 isn't enough: turn off battery optimization for Amber (Android settings, then Apps, then Amber, then Battery, then Unrestricted). Then try step 1 again. 3. If it still doesn't work: use the nostrconnect:// flow instead of bunker://, meaning in Azzamo choose the path where Azzamo shows the QR code and Amber scans it (not the other way around). If Amber initiates the connect, the race condition on Azzamo's side is gone.
thread · root 15d3b120…14c5 · depth 8 · · selected 80d39b8d…62ce
thread
root 15d3b120…14c5 · depth 8 · · selected 80d39b8d…62ce
i get this error almost every time I do anything with Amber, even if I grant full permissions and everything.Please fix my retardation #asknostrnostr:nprofile1qqs02f70juxwyc88gfsjzjlkzt50wkjemvvrtmt7gpfnymplvh3r9mspp4mhxue69uhkummn9ekx7mqpr9mhxue69uhkumm0wfhx7er99ehx7um5wgcjucm0d5q3uamnwvaz7tmzd96xxmmfdekkz6nvd9ejumn0wd68yvfwvdhk6sdfk4xEverything looks fine on Amber's side. Maybe it's a browser issue? i have no ideahttps://image.nostr.build/57fd968af7ed92f1916bd0223c042c1f091354b632568270141cf6ba833ddf2e.jpg
Looks ok on your side. Where is the login page, you have an URL?
I copied the URL into Amber and the connection is all good on that end seemingly then I return to the webpageand 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
Same thing happens with nostrmedia, so it should be something going wrong with my GrapheneOS phone or Amber
I can only guess, but the most common cause would be that the relay in the bunker:// token isn't reachable orisn'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 inAmber using a reliable NIP-46 relay like wss://relay.nsec.app.
Unfortunately, this relay is dead. It was owned by the same guy who built Nostr.band
Thanks for the info. So if I delete wss://relay.nsec.app from the relay list, will it work?
Here's what you can do in 30 seconds on your phone:1. Close the site completely, open Amber and leave it in the foreground, then reload Azzamo and immediately tap"Remote signer". This warms up the relay pool and often bypasses the race condition.2. If step 1 isn't enough: turn off battery optimization for Amber (Android settings, then Apps, then Amber,then Battery, then Unrestricted). Then try step 1 again.3. If it still doesn't work: use the nostrconnect:// flow instead of bunker://, meaning in Azzamo choose thepath where Azzamo shows the QR code and Amber scans it (not the other way around). If Amber initiates theconnect, the race condition on Azzamo's side is gone.
Looks ok on your side. Where is the login page, you have an URL?
Yusuf al-Texani -- 1d [parent] | reply [1 reply]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
Yusuf al-Texani -- 1d [parent] | reply [1 reply]Same thing happens with nostrmedia, so it should be something going wrong with my GrapheneOS phone or Amber
alp -- 1d [parent] | reply [1 reply]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.
d49a9023…a8df -- 1d [parent] | reply [1 reply]Unfortunately, this relay is dead. It was owned by the same guy who built Nostr.band
Yusuf al-Texani -- 1d [parent] | reply [1 reply]Thanks for the info. So if I delete wss://relay.nsec.app from the relay list, will it work?