Nextcloud Turnkey bug?

urza9814

New Member
Nov 13, 2026
2
0
0
Hello All,

I downloaded a fresh copy of Proxmox 9.2-1 this morning, put it on a USB drive, and installed it on a server. Once it was installed I went into the web interface and downloaded the "debian-13-turnkey-nextcloud_19.0.2_amd64.tar.gz" template. I created and booted a container with that template and opened the console, put in a password and hostname as prompted by the init script, and was met with the following error:


Code:
In Config.php line 339:
                                                                  
  Config is set to be read-only via option "config_is_read_only". 
                                                                  

config:system:set [--output [OUTPUT]] [--type TYPE] [--value VALUE] [--update-only] [--] <name>...

Traceback (most recent call last):
  File "/usr/lib/inithooks/bin/nextcloud.py", line 360, in <module>
    main()
    ~~~~^^
  File "/usr/lib/inithooks/bin/nextcloud.py", line 243, in main
    subprocess.run([
    ~~~~~~~~~~~~~~^^
        "/usr/local/bin/turnkey-occ", "config:system:set",
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        "trusted_domains", "1", f"--value={domain}"
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ], env=occ_env, check=True)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/subprocess.py", line 577, in run
    raise CalledProcessError(retcode, process.args,
                             output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/usr/local/bin/turnkey-occ', 'config:system:set', 'trusted_domains', '1', '--value=nc-test.mydomain.com']' returned non-zero exit status 1.
error: Setup stopped at 40nextcloud. Correct the error and run turnkey-init again.

I checked the config.php file under /var/www/nextcloud/config/ but did not find any entry for 'config_is_read_only'. I did try adding that option and explicitly setting it to 'false', but I'm still getting the same error.

Considering that this is a fresh install with fully default configs I'd expect this to "just work"....anyone know what is going on here?
 
Hi urza9814,

Looks like you've encountered an issue with the TurnKey Nextcloud appliance rather than Proxmox itself.

TurnKey Nextcloud 19.0 has been documented to use a separate configuration file named turnkey-read-only.config.php, which explicitly enables config_is_read_only. Nextcloud loads all *.config.php files and their settings override those in the primary config.php. This would explain why your changes aren't taking effect.

You should check the configuration files:

Code:
grep -Rns 'config_is_read_only' /var/www/nextcloud/config --include='*.php'
ls -l /var/www/nextcloud/config/
If you find turnkey-read-only.config.php with that setting enabled, try moving it out of the configuration directory. I.e. as such:

Code:
mv /var/www/nextcloud/config/turnkey-read-only.config.php /root/turnkey-read-only.config.php.disabled
chown www-data:www-data /var/www/nextcloud/config/config.php
turnkey-init
The ownership change also fixes another documented issue with TurnKey 19.0, where config.php is owned by root even though the Nextcloud CLI runs as www-data. The TurnKey developers have also introduced logic in their newer initialization script to remove the legacy read-only configuration, which makes me suspect this as a regression issue for thier newer processes. For some context you can read about it here: https://github.com/turnkeylinux/tracker/issues/2149

If the configuration fragment isn't present, could you share the output of the first two commands? Please don't post the contents of config.php itself, as it contains database credentials from what I recall.

Cheers,


Tmanok
 
Ah! Apologies; I thought these turnkey templates were a proxmox thing! Thanks for pointing out that config file; commenting the contents got it working.