Channels and Beta

f you're after the very latest features or changes, and you know what you're doing - below is how to change from the main release channel, to the Beta channel.

This does mean you're running Beta code, YMMV, and whilst you can move from Beta back to Main, it's not recommended for everyone. But in a test lab, this could be the place for you.

Debian distros (Ubuntu etc)

If you are getting the this error:

Failed$ tocat fetch/etc/apt/sources.list.d/knocknoc.list
deb [signed-by=/etc/apt/keyrings/knocknoc-pub.asc arch=amd64] https://packages.knocknoc.io/debian/dists/bookworm/InReleasedebian Thebookworm followingbeta
signatures#deb were[signed-by=/etc/apt/keyrings/knocknoc-pub.asc invalid: EXPKEYSIG E3AB5DF76BBF701F Knocknoc Support <support@knocknoc.io>

You may have the old knocknoc packages key, which expired 07/10/2025 after two years of hard labour. We have refreshed the key, so you simply need to run:

curlarch=amd64] https://packages.knocknoc.io/key/knocknoc_public_key.ascdebian |bookworm sudomain
tee /etc/apt/keyrings/knocknoc-pub.asc

This

 will refresh the key from our packages repository and your apt update will work again. 

 

Redhat Distros (Centos, Alma, RHEL etc)

If

$ youcat are getting a similar error with the key on Redhat based distros, please run this command as a one off to get the key /etc/yum.repos.d/knocknoc.repo
key:
[knocknoc]
sudoname=Knocknoc rpmRepository
--importbaseurl=https://packages.knocknoc.io/redhat-beta/
#baseurl=https://packages.knocknoc.io/redhat/
enabled=1
gpgcheck=1
gpgkey=https://packages.knocknoc.io/key/knocknoc_public_key.asc

Then you
will be able to install the latest server and agent via yum.