- Joined
- Jun 8, 2022
- Messages
- 14
- Reaction score
- 2
Seems like that SBC Repo isn't signed anymore.Err:7 http://downloads-global.3cx.com/downloads/debian buster InRelease
406 Not Acceptable [IP: 104.18.15.54 80]
Reading package lists... Done
E: Failed to fetch http://downloads-global.3cx.com/downloads/debian/dists/buster/InRelease 406 Not Acceptable [IP: 104.18.15.54 80]
E: The repository 'http://downloads-global.3cx.com/downloads/debian buster InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
I have a workaround for myself:
deb [arch=amd64 by-hash=yes signed-by=/usr/share/keyrings/3cx-archive-keyring.gpg] http://repo.3cx.com/3cx buster main
deb [arch=amd64 by-hash=yes signed-by=/usr/share/keyrings/3cx-archive-keyring.gpg] http://repo.3cx.com/3cx buster-testing main
Those 2 repos from the 3cx controller are working fine.
Just the official for the SBC isn't.
Another question, anyone tryed the SBC on something else as buster? like ubuntu 22.04?
Or at least bullseye?
As far i understand, the SBC hasn't that much todo.
Just running that old buster in an LXC container, is gonna probably break at some time.
However its working actually perfect at the moment, just the repo isn't signed anymore.
Please fix that.
Cheers