Update Core Lightning

General
1

An update (25.02.1) to Core Lightning Node is available on Github, but I cannot find a way to get that update to the CLN on Start9. Do I have to wait until Start9 makes it available? Is there some way to push the update? According to support on Github, I need that update in order to get my CLN to work properly.

2

Hi, we tend to release our updates on the Marketplace after they have been tested and if no bugs are found in the new release, then they are packaged up for StartOS release.

Once the update is available you will see it under your Updates tab on your Server. There is no way to “sideload” updates from github.

3

Thanks for the explanation and information.

4

Following up on my earlier question because a similar issue has come up again with Core Lightning.

My current production StartOS node is on x86_64 and currently runs Core Lightning / CLN v26.04.1. My StartOS Updates page is seeing fresh June 2, 2026 registry updates for other services, including Fulcrum, Mempool, and Tor, but it is not showing a Core Lightning update.

However, the Start9Labs cln-startos GitHub repository shows a 26.6:0 release that appears to package Core Lightning 26.06.

I downloaded c-lightning_x86_64.s9pk from that release and verified the SHA256 hash:

2EDD4C55EC193F446394D832AB4A0AFFB9227F4D0280003F55059C1EC4317AC3

I did not sideload it on my production node.

As a test, I tried uploading that package through the sideload screen on an old legacy StartOS/Embassy v0.3.5.1 node, and the UI rejected it with “Invalid package file.” I assume that may just be because the legacy OS is too old for the newer package format.

Questions:

  1. Is Core Lightning 26.6:0 intended to be available through the Start9 Registry for existing x86_64 StartOS installs?

  2. If yes, why might my server see other June 2 registry updates but not the CLN update?

  3. Is sideloading c-lightning_x86_64.s9pk on a current production StartOS node supported or not supported?

  4. Is the legacy v0.3.5.1 “Invalid package file” result expected for newer .s9pk packages?

  5. What is the recommended safe path to update CLN from v26.04.1 to v26.06?

Context: Megalith LSP suggested CLN 26.06 may fix a connection persistence issue between my CLN node and their LND LSP node. I am avoiding manual binary replacement or unsupported changes because this is a production Lightning node with active channels.

5

My production server is on StartOS 0.4.0-beta.9. I also do not see a Sideload Service option in the System menu on this server. Is sideloading intentionally unavailable in 0.4.0-beta.9, and is CLN 26.6:0 expected to appear through Updates for this beta version?