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
h.
Hey nostr:npub1c878wu04lfqcl5avfy3p5x83ndpvedaxv0dg7pxthakq3jqdyzcs2n8avm,
Your lnbits server finally let me create a new instance on your SaaS, paid to test for a few days, trying to reproduce the error I showed you in the DM's the past few weeks from the other instance
- started new instance
- went to server tab on left side
- changed funding source
- saved new settings
- clicked restart to activate new settings
SAME ISSUE!!! 503 Service Nginx Unavailable!
https://finickycrackers0.lnbits.com/

At least I could reproduce this to show you. This needs serious fixing ASAP. Literally cant even test anything. Will make proper report on Github
Discussion
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



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
nostr:npub1ytm3v8mkup6mnc9z2zjy0zz2czdsfd3kal7hcup6jgu5a5lm885qhup3z6 just tested
Instance was working, until he changed title, saved, restarted. Same 503 error
https://kindpudding5.lnbits.com

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..👇
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 💜