pull down to refresh

I updated to the latest version available in StartOS, and I get this error when trying to create alias, offers, etc:

Fehler: ERROR: failed to connect tonic::transport::Error(Transport, ConnectError(ConnectError("tcp connect error", 127.0.0.1:7000, Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))

Strange that update should prevent this error altogether. Try restarting Bolt12 Pay and if this does not help downgrade to version 0.2.108, not 0.2.108:1
I am pretty depressed right now as it seems when the LND package 0.21 beta will be released custom protocol will not work anymore and this leads to breaking my app completely until the upstream LNDK module project will come up with a fix

reply

oh im so sorry, man that is a real bummer

reply

The fix out and is confirmed working.
I made a modified LNDK module , so Bolt 12 Pay 0.2.109:1

will now work with the current LND 0.20.1 and also with the upcoming LND 0.21. that probably will be out this week.

That was a tough coding session. 😅

reply
reply

Bolt11 , Lnurl, Lightning address was broken as well for LND 0.21😂
So made another fix. Bolt12 pay 0.2.110 is out. Fully tested against LND 0.21.0.

Works smooth now and downward compatible to current official Startos LND package 0.20.1

reply

The fix for Bolt12 Pay working LND 0.21seems found, and I am doing some testing right now

reply

Just double checked Can not reproduce the error my startos app is just working fine

reply

downgrading seems to have fixed it 🤙

reply

I think restart is enough no need to downgrade but will observe and investigate since I got the same error on my umbrel installation.

I am preparing an update for the app description and instructions now, informing that users should stay on LND 0.20.1 beta if they want to continue using this app and not update LND otherwise it will break BOLT12 Pay.

Maybe I can find a fix with Claude code, it says it is not trivial but perhaps doable...

reply

Had the same error on umbrel after a restart of lnd and setting up new channels. After a restart of Bolt12 pay it was resolved for me

reply