Avatar
SUPERMAX 1y ago

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

Reply to this note

Please Login to reply.

Discussion

Avatar
SUPERMAX 1y ago

Anyone who would like yo reproduce this #LNBits error issue I'll support you're testing

This has happened to me every single time I've created an instance on LNBits SaaS.

Avatar
Ben Arc 1y ago

Not sure where you are going wrong, I span up multiple instances yesterday. Are you resetting from lnbits dot com? That'll wipe the settings, something up with your funding source

Avatar
SUPERMAX 1y ago

No. Easy to reproduce by following steps in quoted note.

Just create an instance, change the funding source, get 503 nginx error.

-----

- started new instance

- went to server tab on left side

- changed funding source

- saved new settings

- clicked restart to activate new settings

-----

I have one other person so far who has tested this and could also reproduce bug.

Avatar
SUPERMAX 1y ago

So I assume you can't see anything on your side? You are cometely blind to anyone who makes any instances?

BTW the funding sources I change to are LNBits wallets for quick speed & testing. Maybe you have a bug that LNBits SaaS can't handle requests from any other LNBits wallets?

Be an odd bug..

Avatar
Bitcrazy 🛀 1y ago

This is a great question. We have to test the LNBITS instance as a funding source all the way. I haven't tested that part... But after troubleshooting with you nostr:npub14cgq353exzmhdsvqjtmw4dq7fvyleuls8umyrvd5umhr4gtx6asq7hqjhl earlier, I would agree with everyone above that the funding source config needs specific error logging when we make mistakes in the config (macaroon or address) or when it can't reach out node for whatever reason

Otherwise, Alby and LND Rest (over clearnet) works like a charm --> we've tested Voltage ⚡!!😋

Avatar
SUPERMAX 1y ago

Absolutely 100%!!! Thank you for testing with me much more to test!

Avatar
arbadacarba 1y ago

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.

Avatar
SUPERMAX 1y ago

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

Avatar
SUPERMAX 1y ago

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

Avatar
arbadacarba 1y ago

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

Avatar
SUPERMAX 1y ago

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

Avatar
SUPERMAX 1y ago

nostr:npub1ytm3v8mkup6mnc9z2zjy0zz2czdsfd3kal7hcup6jgu5a5lm885qhup3z6 just tested

Instance was working, until he changed title, saved, restarted. Same 503 error

https://kindpudding5.lnbits.com

Avatar
arbadacarba 1y ago

The payment keeps your instance up for one hour only. After that you'll need to prolong first to come to it again

Avatar
SUPERMAX 1y ago

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

Avatar
arbadacarba 1y ago

Got it but apart from the error screen cannot reproduce with 3 of them all pointing to legend 🙅‍♀️

Avatar
SUPERMAX 1y ago

Thanks for testing I'll share a more formal github link in this thread when I'm finished writing 💜

Avatar
SUPERMAX 1y ago

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

Avatar
arbadacarba 1y ago

Firefox on desktop Mac from D without vpn

Avatar
SUPERMAX 1y ago

So you're saying I need to wait 1 hour after instance starts for it to be restarted properly ?

Avatar
arbadacarba 1y ago

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.