Hey guys, selfhosted noob here, i'm looking in a way to install nextcloud in my proxmox home server in the most simple way possible, i tried following AIO documentation + video helping but i was getting too many problems, whats the most reliable, simplest and secure way of installing?
Thank you guys!
So I'm trying to reinstall NC from scratch now and I want to use Proxmox for a dedicated Nextcloud server. What are the pros and cons so I do it right the first time? Ideally I want to install in an LXC. I've experimented with various methods and had mixed results.
Any thoughts?
-
Turnkey Linux LXC
-
Tried this, would randomly go 100% CPU & Mem and lock up
-
-
Ubuntu LXC with NC installed with Snap
-
Getting random errors
-
-
Debian LXC with docker and use NC AIO
-
Read that docker in LXC isn't best practice?
-
Trying to avoid Apache issues that I had in the past
-
-
Full Debian VM with docker and use NC AIO
-
Used in the past, high memory usage
-
-
Others?
I've noticed a number of posts where users are having issues with integrating the latest fork of Euro Office with NextCloud 34 so for anyone looking to set this up from scratch I've created a guide here:
https://github.com/Rich-Hacks/eurooffice-nextcloud
The guide was created from my own knowledge, and assistance from Claude and Mistral Le Chat - it covers a number of issues that I ran into including nginx errors, apt install overwriting my config, and issues with the editor loading but changes not saving.
Happy to answer any questions, or assist with any issues than anyone is running into. Hope this helps anyone that's stuck!
The design
-
Separate LXC, not co-hosted on the Nextcloud VM — the document server is heavy (Node.js, PostgreSQL, RabbitMQ, Redis, nginx), is updated on its own cadence, and can be rebooted/rebuilt without touching Nextcloud.
-
Apache name-based vhost rather than a new port — router forwards 80/443 to the Nextcloud VM. A second vhost on the same 443, routed by SNI/Host header, avoids non-standard ports and extra firewall rules.
-
Public DNS is mandatory — the editor JavaScript loads in the user's browser directly from the document server (Nextcloud only embeds it in an iframe), so the document server URL must resolve and be reachable from wherever the user sits. Server-to-server callback traffic stays on the LAN via the connector's internal-address settings and an
/etc/hostsentry. -
DNS-01 (Cloudflare) for the new certificate — no dependency on port 80, renews unattended, and coexists with the TurnKey appliance's existing dehydrated/HTTP-01 renewal for the Nextcloud certificate.
For me this is a replacement for Microsoft Office, I've tested it on Fedora 44, a Surface Pro and a Samsung S25+.
Thank you to anyone can direct me into the right direction. There seems to be several ways to install Nextcloud into a VM. Can anyone point me into pros and cons and which might need best for a small company to use, maximizing features and speed?
The NextcloudPi , AIO and the regular version?
Hi!
I have a server that currently has Nextcloud installed on bare metal, alongside a bunch of other things, and it has become an unmanageable broken mess, so I'm reinstalling everything on containers / VM on Proxmox for isolation.
The host machine for this has a couple of 4TB SATA SSDs that I will combine into a mirrored ZFS pool, which will be dedicated to data storage for Nextcloud. I also wanted to periodically back up this data to some offsite server, either using zfs send, or something like rsync.
My understanding is that:
-
The cleanest / simplest way to install Nextcloud is to use Nextcloud AIO
-
For security reasons, Nextcloud AIO should be installed on top of a VM, not a container (plus, conceptually it feels a bit clunky to me to nest containers with Docker inside an LXC)
-
I cannot mount directories inside a VM (or can I? I see virtiofs being mentioned for that purpose - if that matters, I plan on using Debian or Ubuntu for the guest OS)
What is the cleanest way to achieve what I want to do? I see a few ways forward:
Option 1: ZFS pool inside the guest
I would pass the raw SSDs to the VM, and create a ZFS pool and dataset within the VM.
Pros:
-
No need to worry about user mapping between proxmox and guest
Cons:
-
Need to set up backups inside the VM
-
I lose the monitoring of the ZFS pool from within the Proxmox UI
Option 2: Zvol passed to the guest
I would create a ZFS pool and zvol in Proxmox, and pass the zvol to the VM for storage.
Pros:
-
Simple
-
Monitoring of the ZFS pool from within the Proxmox UI
Cons:
-
Data opaque to Proxmox - need to set up backups inside the VM
Option 3: Share through NFS / Samba
I would create a ZFS pool and dataset in Proxmox, and mount the dataset into an LXC container than exposes it to the VM through Samba or NFS.
Pros:
-
Backup can be configured on the Proxmox host
-
Monitoring through Proxmox
Cons:
-
More complicated (1 extra container)
-
Need to figure out how to map users
-
Possible loss of performance?
Option 4: Virtiofs
I would create a ZFS pool and dataset in Proxmox, and expose the dataset to the VM through Virtiofs.
Pros:
-
Backup can be configured on the Proxmox host
-
Monitoring through Proxmox
-
Simpler conceptually?
Cons:
-
Is it stable?
-
Possible loss of performance?
I'm a bit concerned because I see some complaints about Virtiofs being slow:
-
https://www.reddit.com/r/Proxmox/comments/18ujo9m/is_virtiofs_reliable_and_easy_in_proxmox_81/
-
https://forum.proxmox.com/threads/i-want-to-like-virtiofs-but.164833/
Thanks!
So the title really says it all, I want to know what is the best way to use Nextcloud on Proxmox, Ive got experience with Yunohost and Nextcloud and a little bit with Webmin and Ubuntu.
I have tried every single thing I've found so far to try and get this installed. I have tried VM in Proxmox, in LXC, in Docker, every tutorial I have found and tried to do step-by-step has not worked. Is running Nextcloud on Proxmox even a thing anymore?
EDIT: Wow, thanks for all the responses. I haven't really checked on any of this stuff yet because I was out of town but I'm going to try it in the next day or two. A quick glance of all the advice and responses shows me a lot of what you all have mentioned didn't work for one reason or another, but I honestly tried so many things with nothing working that I can't specifically remember the errors I got when trying it, so I'll try them again.