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.
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..
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 ⚡!!😋
Absolutely 100%!!! Thank you for testing with me much more to test!
