On 9/14/25 12:27, A. F. Cano via Freedombox-discuss wrote:
Hello,Since I was able to boot the newly upgraded FreedomBox (Thanks Sunil - see the HELP! thread), i noticed some anomalies (34 diagnostic failures) but all but 2 were solved by the "try to repair" button and, presumably the recent update of the FreedomBox software. Most of the failues were in the ejabberd and mstrix-synapse apps. The latter being critical for me, I was really happy that the "try to repair" button fixed it after 2 tries, possibly also thanks to some packages that were recently updated. the 2 failures that remain are not critical. The first one: Let's Encrypt: Access URL https://freedombox seems to have no ill effect and has been there for a very long time. I wonder if it has something to do with having renamed my FreedomBox to fbx (that is what hostname returns).
You can ignore this error. If you have domain called "freedombox" added to your domains list in System -> Name Services, you can remove it (since this is not a proper domain name anyway) and the error will go away.
The other one is: Searx: Package searx is not available for install Since it was giving other errors, I thought that maybe uninstaling it would force a re-install of the current version, but it now appears that searx is not in stable or testing, only in sid, so I'll have to wait until is propagates.
Unfortunately, Searx will not be available for Trixie as the upstream is no longer maintained. No one has stepped forward to package the searx-ng package which is it be its replacement. We are sad to the app become unavailable.
Other than these 2 explicit diagnostic failures, a few services didn't start, but doing so manually from cockpit seems to have fixed all of them except 2: apparmor and uwsgi. I see no visible signs of anything caused by these non-starts. Others that eventually started had to do with collection of statistics, so now everything works in cockpit, also logrotate is one that I remember. Overall, great work Sunil and other developers. I like the new features. Thanks a lot.
There are other users who have reported issues with apparmor. This likely a Debian packaging issue due to leftover profile files in /etc/apparmor.d/. Please follow this issue here[1].
We have not seen any uwsgi related issues so far. Please report the issue with more details.
Links: 1) https://salsa.debian.org/freedombox-team/freedombox/-/issues/2537 -- Sunil
OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
