Oddbean new post about | logout
 Weird way to report an issue. Tested with a wallet on legend as funding source - worked. But I see the error too, wait a second and press refres https://image.nostr.build/cd2c2faa07725c0988010b8a81ae1be0a3ce778c3a8f58cf71e112dcd0c189ca.jpg h. 
 My github was unavailable for a weird reason. Filed a support ticket and it was resolved. 

I am still waiting for my instance to be come back. Can you see this SaaS? Maybe its on my end

https://finickycrackers0.lnbits.com/
Thanks for testing with me 
 Just created entire new email & password

New instance 
https://adoringcardinal1.lnbits.com

Created a legend.lnbits free wallet

Updated funding source on the adoringcardinal1 instance 

Saved, restarted server with legend.lnbits wallet

Same 503 enginx error


Third time in a row for me; very consistent bug
 https://image.nostr.build/7e313e85d3ef9efb849ed5f820ee69ba8169596f865ae09252e6bda5ce618555.jpg
 https://image.nostr.build/057880964984ca6445a60b2ef7c11c96bb3337e5522936087d2f1c54d41090d6.jpg
 https://image.nostr.build/5ec54e2edf4836ac147f4508a6ac370736b240bf23912ffdc0bdcd0b20f84b34.jpg

I'll screen record the entire process to quadruple verify. Multiple people have now been testing this. Writing formal github bug issue & tagging all nostr events associated with this
 
 The error appears also if the first paid  1h is over. Login from LNbits.com instead of via bookmark worked for 3 instances I spun up  
 I haven't saved these as bookmarks

Always clear cache and go to lnbits.com and type in credential's 

I guess I'll go try on friends device on their internet  
 @Bitcrazy 🛀 just tested
Instance was working, until he changed title, saved, restarted. Same 503 error

https://kindpudding5.lnbits.com
 https://image.nostr.build/04d76ecf34714a3d35ea9975c40842a96c8d719722d3f9667a5493a2a4c17502.jpg 
 Fourth reproduction👇
nostr:nevent1qqsznpq38t2ruftyctqc62c9tsedx5qlcsme8vuu3q7l800najug96cpr3mhxue69uhhyetvv9ujumt4w35ku7thv9kxcet59e3k7mgzyzhpqzxj8yctwakpszf0d645re9snl8n7qlnvsd3knnwuw4pvmtkqqcyqqqqqqg0ua8g0 
 The payment keeps your instance up for one hour only. After that you'll need to prolong first to come to it again 
 I usually pay at minimum 210 sats (~10 hours) yo give the server time to refresh. I get it things will not happen immediately, maybe 5 minutes or so. But not hours+ . even weeks on my other instance. 



Funded this one ~ 2 months ago, still 503 error
Paid 50k SATs (paid through July 1st 2024). Haven't used it for more than ~12 hours..👇

https://obsessedjerky7.lnbits.com 
 Got it but apart from the error screen cannot reproduce with 3 of them all pointing to legend 🙅‍♀️ 
 Thanks for testing I'll share a more formal github link in this thread when I'm finished writing 💜 
 Idk if this is affecting anything, but do you mind sharing where you are accessing your instance? For me;

In USA (east coast), via brave browser through VPN 
 Firefox on desktop Mac from D without vpn 
 So you're saying I need to wait 1 hour after instance starts for it to be restarted properly ? 
 No, setting up took around 5min each, then configured and restarted, error screen, refresh, fine. Login on LNbits.com offers all of them within first h. Prolonging also works from there.