Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 24 has issues, how to upgrade to version 23? #7361

Open
nakoshi-satamoto opened this issue Jun 1, 2024 · 6 comments
Open

Version 24 has issues, how to upgrade to version 23? #7361

nakoshi-satamoto opened this issue Jun 1, 2024 · 6 comments

Comments

@nakoshi-satamoto
Copy link

See issue #7180

Ever since going to version 24 and sub versions after 24, I have had issues with having successful outbound payments. The log file also gets filled with gossip related errors. Is it possible to safely go back to version 23?

@grubles
Copy link
Contributor

grubles commented Jun 1, 2024

Is that while using the pay plugin or renepay? I don't think you can move back to 23.x since moving to 24.x would have likely upgraded your database and there is no support for downgrading.

@nakoshi-satamoto
Copy link
Author

nakoshi-satamoto commented Jun 1, 2024 via email

@crc32
Copy link

crc32 commented Jun 2, 2024

I cannot pay using Ride The Lightning, pay or renepay.

renepay results in:
{ "code": 205, "message": "Destination is unknown in the network gossip." }

This is paying to strike, which I can pay just fine to from LND.

@chrisguida
Copy link
Contributor

No, there is no way to downgrade your database to a previous version. If you want a previous version, spin up a new node.

@vincenzopalazzo
Copy link
Contributor

If you want a previous version, spin up a new node.

Unfortunatly this is bad, but this is the only way that you have to run a previous version. However, this is a tech solution not a real one because you can not bring your channels with you.

@whitslack
Copy link
Collaborator

There aren't that many database schema changes between releases of CLN. If you were desperate, you could manually reverse the changes in your database.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants