Why BeAdmin doesn't detect its own updates and how to fix it
Settings → System has a section called «Software version and updates». It shows the «Current version» of BeAdmin and either offers a new one or reports «You are up to date» — the panel gets this status by checking your server's own software sources for a newer BeAdmin package.
Sometimes a newer BeAdmin version is out, but the panel still reports «You are up to date» after pressing «Check for updates». This almost always comes down to the server's software sources, not the panel itself — check the reasons below in order.
A major OS upgrade disabled BeAdmin's software source
BeAdmin installs from its own apt repository, added to /etc/apt/sources.list.d/beadmin.list during setup (see the Installation guide). When the server's operating system is upgraded to a new major release — for example Ubuntu 22.04 to 24.04, typically via do-release-upgrade — the OS upgrader disables every third-party software source it finds, including BeAdmin's, and does not turn them back on afterward.
In practice it renames /etc/apt/sources.list.d/beadmin.list to beadmin.list.distUpgrade (and beadmin-vendors.list the same way, if you have a VPN module such as AmneziaWG or Mimicry installed). With the source disabled, the server no longer sees new BeAdmin packages at all — so the panel reports «You are up to date» no matter how far behind it actually is.
How to check:
apt-cache policy beadminIf the only source listed is /var/lib/dpkg/status and there is no https://… line for beadmin, the source is disabled. You can also check the sources directory directly:
ls /etc/apt/sources.list.d/A beadmin.list.distUpgrade file there confirms it was the OS upgrade that disabled it.
How to fix:
sudo mv /etc/apt/sources.list.d/beadmin.list.distUpgrade /etc/apt/sources.list.d/beadmin.list
# only if this file exists (VPN modules):
sudo mv /etc/apt/sources.list.d/beadmin-vendors.list.distUpgrade /etc/apt/sources.list.d/beadmin-vendors.list
sudo apt-get updateGo back to Settings → System and press «Check for updates» again — the new version now shows up.
The server can't reach BeAdmin's software source
A blocked outbound connection, a firewall rule, or a proxy in front of the server can stop it from reaching BeAdmin's repository — the panel then reports the same «You are up to date» status, since it never got a response with a newer package list.
Run the update and check whether it reports an error specifically for the BeAdmin repository line:
sudo apt-get updateIf it does, make sure the server can reach it — allow outbound HTTPS, check firewall and proxy rules — then retry.
The package index is stale or apt is in a broken state
Occasionally sudo apt-get update fails outright with a signing-key error rather than a network error, and apt keeps using the last index it managed to fetch — which may predate the new release. Fix the key error apt reports (re-import the signing key it names) and run the update again:
sudo apt-get update