Admins will be upgrading ORNL GitLab Servers on Saturday, 16 May 2026, from 7 AM until 11 AM EST. Repositories will experience intermittent outages during this time.
@@ -196,6 +196,8 @@ Available as [services.patroni](options.html#opt-services.patroni.enable).
- The `p4` package now only includes the open-source Perforce Helix Core command-line client and APIs. It no longer installs the unfree Helix Core Server binaries `p4d`, `p4broker`, and `p4p`. To install the Helix Core Server binaries, use the `p4d` package instead.
- The NextCloud NixOS module uses OpenSSL 3.x for its PHP's openssl extension, this breaks RC4-based server-side encryption in NextCloud, making all your files unreadable upon upgrade. Upon testing, we could not trigger any cases of **data loss**, but we **cannot guarantee** that for every accidental OpenSSL upgrade. To restore functionality, [`services.nextcloud.enableBrokenCiphersForSSE`](#opt-services.nextcloud.enableBrokenCiphersForSSE) has to be set to `true`. NextCloud is planning to implement AES-256-GCM server-side encryption in the future through <https://github.com/nextcloud/server/pull/25551>.
- The `coq` package and versioned variants starting at `coq_8_14` no
longer include CoqIDE, which is now available through
`coqPackages.coqide`. It is still possible to get CoqIDE as part of
# Optionally enabled depending on caching settings
++optionalcfg.caching.apcuapcu
@@ -80,6 +85,36 @@ in {
options.services.nextcloud={
enable=mkEnableOption(lib.mdDoc"nextcloud");
enableBrokenCiphersForSSE=mkOption{
type=types.bool;
default=false;
description=lib.mdDoc''
This option uses OpenSSL PHP extension linked against OpenSSL 1.x rather
than latest OpenSSL (≥ 3), this is not recommended except if you need
it.
Server-side encryption in NextCloud uses RC4 ciphers, a broken cipher
since ~2004.
This cipher has been disabled in OpenSSL ≥ 3 and requires
a specific legacy profile to re-enable it.
If you upgrade to a NextCloud using OpenSSL ≥ 3 and have
server-side encryption configured, you will not be able to access
your files anymore, enabling this option can restore access to your files.
Unless you are using external storage,
it is advised to [disable server-side encryption](https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/encryption_configuration.html#disabling-encryption) as it is unclear
it provides any amount of security beyond encryption for external storage.
If you know more about this feature and is keen on it,
please chime in <https://github.com/NixOS/nixpkgs/pull/198470> or open
an issue in nixpkgs.
In the future, NextCloud may move to AES-256-GCM, by then,
this option will be deprecated.
'';
};
hostName=mkOption{
type=types.str;
description=lib.mdDoc"FQDN for the nextcloud instance.";
You're using PHP's openssl extension built against OpenSSL 1.1.
This is only necessary if you're using NextCloud's server-side encryption.
Please keep in mind that it's using the broken RC4 cipher.
In order to disable this option and remove this warning,
server-side encryption has to be disabled, see <https://docs.nextcloud.com/server/latest/admin_manual/configuration_files/encryption_configuration.html#disabling-encryption> on how to achieve this.
For more context, here is the implementing pull request: https://github.com/NixOS/nixpkgs/pull/198470
'')
++(optionalisUnsupportedMariadb''
You seem to be using MariaDB at an unsupported version (i.e. at least 10.6)!
Please note that this isn't supported officially by Nextcloud. You can either