Lightning connection error after upgrade to latest varsion #5497
-
|
Hello, I would like to ask for your help - after the upgrade of my manual installation of BTCPayServer to the lastest varsion and rebuilding I get this error when trying to run
Any advice appreciated! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 21 replies
-
|
Thanks for reporting! Please upgrade only to released versions and associated tags, right now you seem to be running straight from git checkout $(git tag --sort -version:refname | awk 'match($0, /^v[0-9]+\.[0-9]+\.[0-9]+$/)' | head -n 1)Please checkout the latest tagged version and rebuild. As for the error, we need to fix this, @Kukks. |
Beta Was this translation helpful? Give feedback.
-
|
Will need a new version of LNbank published. Likely in conjunction with BTCPay Server v1.12 — no ETA yet, but #soon. |
Beta Was this translation helpful? Give feedback.
-
|
Looking forward to v1.12 then. Thank you guys for all the help! You are working on an amazing product! |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I did the same thing (wrong from my side), updated from the master, and now I have the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
Deleting the plugin does not delete the database contents, so the data will still be there after the upgrade/reinstall. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I see. Thank you very much for your quick response and for the great work on this fantastic project, love it!!! |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
Thanks for reporting! Please upgrade only to released versions and associated tags, right now you seem to be running straight from
master, which should not be used for production deployments. You can check out the latest tag with this command:git checkout $(git tag --sort -version:refname | awk 'match($0, /^v[0-9]+\.[0-9]+\.[0-9]+$/)' | head -n 1)Please checkout the latest tagged version and rebuild.
As for the error, we need to fix this, @Kukks.