alp -- 1d nostr:npub1jjn20zj6awa6gz73423zxjqszvkzmqqyhwghwctvgy7ncrwlxg8qdavknm , nostr:npub1p6xyr6u5vet33r4x724vxmp9uwfllax5zjdgxeujyrtxt90lp74qvah0rm do you have an idea? It would help enormously if the relay reason were included in the output instead of just "Subscription closed". reply [2 replies]nostr:npub1jjn20zj6awa6gz73423zxjqszvkzmqqyhwghwctvgy7ncrwlxg8qdavknm , nostr:npub1p6xyr6u5vet33r4x724vxmp9uwfllax5zjdgxeujyrtxt90lp74qvah0rm do you have an idea? It would help enormously if the relay reason were included in the output instead of just "Subscription closed".
thread · root 15d3b120…14c5 · depth 6 · · selected fe1fe95c…4de7
thread
root 15d3b120…14c5 · depth 6 · · selected fe1fe95c…4de7
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.
nostr:npub1jjn20zj6awa6gz73423zxjqszvkzmqqyhwghwctvgy7ncrwlxg8qdavknm ,nostr:npub1p6xyr6u5vet33r4x724vxmp9uwfllax5zjdgxeujyrtxt90lp74qvah0rm do you have an idea?It would help enormously if the relay reason were included in the output instead of just "Subscription closed".
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.
aight so— been debugging relay output stuff before and yeah, that "Subscription closed" is pretty vague when you're trying to figure out what actually broke. are you hitting this on a specific relay or does it happen across the board?
Hey nostr:nprofile1qy2hwumn8ghj7ct4w35zumn0wd68yvfwvdhk6qg6waehxw309ahx7mmjdehkgefwdehhxarjxyhxxmmd9uqzqk4402083g9q6yv84l8u94xh6tuz54etzmj302fy7e5gdledg09h7dk9uy , That seemed to be a login bug on mobile where the app closed the connection when you go to another app on your phone to sign the request. Should be fixed now. Let us know if it has been resolved.