Looking for a "best practice setup" for ISPConfig 3.x and Nextcloud and NC 32.x

If you are running an ISPconfig you comne along that people wanna install nextcloud into thier webspace. all right. but here the problems start.

mayn say, well put it into a docker and you are done. OK, but i hate docker.

so i am right now with a 32.X and well it runs, but not as it should be. from cron issues ( cron is installed as demanded in that admin docu and still does not work) to Security & setup warnings that runs in a constant loop with no output.

A LOT of depricated messages in the log, that distract you from the problems. Then php security settings that colide with what NC wants.

right now it looks like a config nightmare and something i wanna replace.

so i hope you guys can shade some light on me , to clear this up und running right.

let me know what u wanna know in detail and we start.

thank you

PHP-Version: 8.3.27
• PHP-FPM: active
• Memcached: active
• APCu CLI enabled: On
• disable_functions:

PHP 8.3.27 (cli) (built: Oct 27 2025 20:46:26) (NTS)

:magnifying_glass_tilted_left: Prüfe PHP CLI Module…
:white_check_mark: Modul geladen: apcu
:white_check_mark: Modul geladen: memcached
:white_check_mark: Modul geladen: gd
:white_check_mark: Modul geladen: curl
:white_check_mark: Modul geladen: zip
:white_check_mark: Modul geladen: dom
:white_check_mark: Modul geladen: mbstring
:white_check_mark: Modul geladen: simplexml
:white_check_mark: Modul geladen: xmlreader
:white_check_mark: Modul geladen: xmlwriter

:white_check_mark: apc.enable_cli ist aktiviert

:white_check_mark: Keine deaktivierten Funktionen in FPM

:white_check_mark: Memcached PHP Modul aktiv (Version 3.3.0)
:white_check_mark: Memcached-Dienst läuft

:white_check_mark: PHP-FPM läuft (php8.3-fpm)

Still valid ?

opcache.memory_consumption=256
opcache.interned_strings_buffer=64
opcache.max_accelerated_files=100000
opcache.enable=1
opcache.enable_cli=1
opcache.memory_consumption=128
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=10000
opcache.revalidate_freq=1
opcache.save_comments=1
memory_limit = 512M

Well, the documentation mentions a lot of points you can get through. For a decent performance, the default configuration of a php/db setup is not the best. Redis/Apcu caching helps a lot to reduce database usage, and the database itself has some caching that can be optimized (the standard cache sizes are often not the best for the Nextcloud usage). Then you have specific webserver configuration, especially for nginx you have templates. For talk and notifications, you have high-performance backends, for the talk to allow larger meetings, and the notifications to have real push notifications to reduce polling through NC clients (also rather large setups).

If you have a “manual” setup, you have to go through these steps manually and find the right settings for yourself. To avoid starting from zero, there is a Nextcloud virtual machine:

and also a setup script to run Nextcloud on Debain/Ubuntu:

they might be some inspiration what parts you might want to touch in your default configuration.

Someone has done the optimization for you, so for smaller setups most things are already done and they anticipate future changes. For you it remains a bit of a black box.

Hi tflidd,

thank u for your answer. The problem with these links is, that they are all standalone installations in an container of some sort.

Like proxmox .

Well i have ISPConfig. Thats a complete other story because it’s an admin panel like plex.

The php security settings you have to turn down in oder to get nextcloud running , well a bummer , sort of.

But it still wont run the right way. so i guess i am still missing something.

or are those links the sub message: you better place that thing as a stand alone, so it can run as it should?

For us the problem is, that it comes down to the inner workings of ISPConfig or other admin panels we are not familiar with.

They are probably to isolate different user accounts between each other. There is for example the server-info app that shows a lot of details of available disks, memory and other parameters of your system, that is something you don’t want to do on a shared environment. But this app is not essential, so you can live with that.

I don’t see an easy way to do that. You have to go through all of that, but in the end there is always the risk that there might be a crucial security setting for your environment which is not compatible with Nextcloud.
We had people here using Nextcloud in shared hosting, for some it was not working at all, for some it was working. But for shared hosters, it was difficult to know any details about their setup, so hard to tell with there was one among them with ispconfig where it worked (and if it works without problems, people won’t come on the forum).