mastodon 4.3.4Mobile-first app to self-host services without pain.*
Put provider access tokens, and get a personal server with Nextcloud, Bitwarden, Jitsi and other services in 25 minutes, fully automated. Then, manage your server from the same mobile app: change preferences, manage storage, set up backups, monitor resource usage.
* We're in public beta testing, so some pain might still occur. We're happy to help you with any problems you encounter via our support chats, email or this fediverse account.
We're releasing the major upgrade to NixOS 25.11 tomorrow. As usual, please make sure that your system disk has at least 6 GiB of free space; you will be able to reclaim the disk space after the upgrade.
Nextcloud will be upgraded to version 32. If you haven't upgraded since July, please do it now to make sure Nextcloud is on version 31. Skipping major versions is not supported by Nextcloud.
SelfPrivacy 0.13.0 is out now, and it finally brings Single Sign On support, powered by Kanidm under the hood.
New servers will have it enabled by default, but for existing ones there are some caveats: please read our blog post for more info: https://selfprivacy.org/blog/2025/04/25/version-0.13.0-release/
We've also added a new service to our catalog: the to-do app @vikunja@social.linux.pizza. It supports SSO out of the box.
This release is made possible thanks to the support from @NGIZero@mastodon.xyz, thank you very much!
SelfPrivacy finally got into Apple TestFlight!
https://testflight.apple.com/join/LPklpjxs
You can now test our app on iPhones and iPads. Feedback and bug reports are very welcome.
(Please note, Hetzner is still experiencing an outage, and it is currently impossible to create a new server with SelfPrivacy on Hetzner)
We've added two new services to our catalog:
— Matrix, a federated messenger with end to end encryption. Right now our integration is experimental and we plan to add more features in the future. If you experience any issues, please report them to us.
— Hedgedoc, a collaborative markdown note editor. You can use it to edit markdown documents with others in real time, and publish them as simple web pages.
Both services fully support our SSO implementation.
Due to new Apple policies, SelfPrivacy wasn't available on iOS for some time. We've resolved the issue, and SelfPrivacy is available on TestFlight once again.
https://testflight.apple.com/join/LPklpjxs
Because Apple can deactivate SelfPrivacy app on your device at any moment, we encourage you to have a recovery key.
We've also published SelfPrivacy 0.13.4. Downloads and changelog: https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/releases/tag/0.13.4
New service is available in SelfPrivacy! Actual Budget (https://actualbudget.org/) is a privacy-focused app for managing your finances, and it is the first service contributed to SelfPrivacy by the community. Big thanks to @cl0vr@tech.lgbt for developing the module and sharing their experience.
Actual Budget supports SSO but doesn't support automatic admin permissions. The first user to log in will be an admin, and permissions of others can be managed in the app's interface. You can install Actual by upgrading your server to the newest version and then going to the Services catalog in your SelfPrivacy app.
(A note for fellow GrapheneOS users: the Actual Budget web app requires JavaScript JIT permission that you might need to enable in Vanadium's website settings)
There are issues with @hetzner@mastodon.hetzner.social API that make it impossible to deploy a new server there using SelfPrivacy right now.
The 'volumes' field in their server creation endpoint [1] no longer attaches volumes, and this breaks our NixOS installation process. There were no changes in their API changelog, and we feel that this [2] incident might be related.
The current workaround would be to quickly attach a volume manually after the app creates the server but before the app launches the server.
You might also get the 412 error in some regions, meaning Hetzner can't fulfill your order. The SelfPrivacy app can handle this, and will show an error.
In the next app update, we will add additional checks to handle situations with unattached volumes, but we think that it is an issue on Hetzner's API side.
[1] https://docs.hetzner.cloud/reference/cloud#servers-create-a-server
[2] https://status.hetzner.com/incident/85d49ac4-5ed8-4458-a0ef-8b8d7fd1a73b
We've just released SelfPrivacy API 3.6.2. This patch fixes the following issues:
— Fixed a regression introduced in 3.6.1, where the Self-Service Panel returned a 500 error when creating an email password for DeltaChat.
— Email passwords are now generated as passphrases, making them easier to use without compromising on security.
— Reduced the number of requests to Backblaze. No more annoying emails from Backblaze about quotas.
— Fixed an issue where servers on Hetzner couldn't boot with a 50% chance. This is a two-stage fix, and you will need to upgrade your server twice to apply it.
Upgrade your server to install the new version. If your server has automatic updates enabled, it will be applied automatically within the next 24 hours.
We're releasing the major upgrade to NixOS 25.05 tomorrow. Please make sure that your system disk has at least 6 GiB of free space; you will be able to reclaim the disk space after the upgrade.
Also, make sure that your SelfPrivacy app is at the latest version (0.13.1); otherwise, real-time updates will stop working.
Small server-side update today.
— Nextcloud should be faster and more responsive now
— You can now disable Nextcloud maintenance mode from the app, without using SSH
— Fixed an issue when servers of former SSO testing participants didn't fully switch to the primary branch
— Improved security hardening of the Vikunja module
Upgrade your server to apply.
We are also testing the major update of system components, which we will probably release tomorrow (if everything goes well). It will require several gigabytes of free space on your system disk.
We’re rolling out an important Kanidm security fix for SelfPrivacy servers tomorrow. (https://github.com/kanidm/kanidm/security/advisories/GHSA-xxwr-vvr3-2g9f) This vulnerability can only be exploited by users of your server that you've created in the "Users" tab. Unauthenticated users cannot do that.
If automatic updates are enabled, your server will update normally.
If you have automatic updates turned off, please run a server update in the SelfPrivacy app as soon as possible so your server receives the NixOS configuration update needed to use our binary cache and apply the Kanidm fix faster. Otherwise your server will have to rebuild Kanidm from sources, which will likely fail due to memory constraints.
We're shipping the fix ourselves instead of waiting for nixpkgs upstream due to severity of the issue. We've already done this before, because it usually takes several days for nixpkgs to release new versions. This time we've added our own binary cache with pre-built packages, because building Kanidm requires at least 4 cores, 16GB+ of RAM, and over 4 hours of time. Most of the SelfPrivacy deployments would just crash trying to compile it.
This cache will also speed up rebuilds overall, because it includes other services that your server has to compile on its own, like Vikunja or our own server-side components.
Side note about recent Linux kernel vulnerabilities in the news: SelfPrivacy instances are not affected, because they use a hardened Linux profile. It will be dropped in the next NixOS release, so we will continue maintaining it ourselves. But in any case, reboot your server from time to time to ensure you're running on the latest kernel.
