From my perspective, this setup is unnecessarily complex and introduces layers that only make things more fragile and harder to manage.
Running Nextcloud as an app inside TrueNAS Scale, which itself runs as a virtual machine on Proxmox, doesn’t make much sense in terms of reliability and maintainability.
This kind of architecture:
- reduces overall stability,
- makes troubleshooting difficult (where exactly is the problem — TrueNAS, Nextcloud, Docker?),
- and adds performance overhead — especially for disk and network I/O.
If you’re already using Proxmox, the most straightforward and stable solution is:
→ a dedicated VM running a Linux server with Nextcloud AIO.
(I also wouldn’t recommend using an LXC container in this case, since Nextcloud AIO runs Dockers inside, and Dockers inside LXC can lead to compatibility issues.)
TrueNAS definitely has its strengths — it’s a great NAS or network storage backend via NFS or iSCSI.
But in this setup, it becomes just another layer that introduces unnecessary complexity.
Just to sum it up: this kind of multi-layered architecture might seem attractive at first glance, but in practice, it often brings more issues than benefits.
I’ve found that keeping things simple works best — either use TrueNAS as your NAS, or run Nextcloud as a standalone solution.
Trying to combine both in a single stack usually results in harder maintenance and increased risk of failure.
Note: This post was written with the help of an AI assistant as a writing aid only. The opinions, solutions, and technical recommendations are fully based on my personal experience.
More about how and why I use AI to write forum posts:
Is there limitations to installing Nextcloud via CT template on Proxmox - #4 by vawaver