FreePBX Distro v17 package server maintenance is scheduled from 2026-02-25T05:30:00Z→2026-02-25T06:30:00Z. apt level new installs e.g. using the shell script or BETA ISO, as well as existing system updates, may be briefly unavailable, delayed or inconsistent during this time. (FreePBX module mirror servers are not part of this notice.)
1 Like
A post was split to a new topic: Upgrading GPG key and fail2ban
Did you decide to remove the prod repo? Is there any news about this ?
I already replaced the gpg keys that expired today, but the whole repo is broken.
Are we supposed to switch to the freepbx17-dev repo ?
E: Failed to fetch http://deb.freepbx.org/freepbx17-prod/dists/bookworm/InRelease 403 Forbidden
E: The repository 'http://deb.freepbx.org/freepbx17-prod bookworm InRelease' is no longer signed.
edit: my bad, i’m using apt-cacher-ng and had to wipe the cache
Howdy! Welcome to the forums.
apt-cacher-ng is a great tool – need to revisit its use in the ISO – thanks for sharing the cache clearing tip! As for details, was it a matter of rm’ing the packages in the cache server or something else more subtle ?
1 Like
Just to clarify it has nothing to do with Freepbx.
apt-cacher-ng is a drive-by cache, all my hosts have it installed and are configured to use it as a proxy for apt.
I cleared the whole freepbx repo on the cache server, but the release files should have been enough.
Your cloudfront cdn does not set a Cache-Control header so the files are not automatically rechecked by apt-cacher-ng, e.g. the debian repo has it set to 2 hours Cache-Control: public, max-age=120 and i have the default timeout set rather high (24h)