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?

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'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

1. 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.

2. 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.

3. 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/hosts entry.

4. 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+.

Basically, do I need to spin up a VM Ubuntu or Debian server and install NC on that? Or is there an NC standalone vm? There are so many youtube tutorials, many of which are outdated or too complex.

What I have:
Proxmox running on Ryzen 3400G and 16GB RAM

TrueNAS Scale running as VM on this. One 2 TB SSD raid pool and one 4TB HDD raid pool.
A 512 GB OS nvme on which everything is installed.

a fresh new domain on Cloudflare - unattached to anything yet

What I want:

A NextCloud instance installed on my SSD pool, with user data directories on HDD pool preferably.
A way to connect to this instance using my new domain, outside of the local network.

I know that installing NC on TrueNAS would be the popular advice. But TrueNAS just updated to the latest version and I can't seem to find any new tutorial for it.

My Linux skills are beginner level. I can follow along most written or video tutorials but can't solve problems on my own. Any help is appreciated. Thanks for reading.

I need a google docs/office 365 replacement. I want to access it using my Tailscale VPN (no reverse proxy, no port forwarding). I want to use my nfs-share on my NAS as storage (mounted locally as /mnt/data).

I'm not an IT-guy so this took me hours and hours. But this works for me. I guess. I'm not sure if I just build some horrible creation so feedback is highly appreciated.

Some learnings.

• Do NOT use the build in Collabora Online - Built-in CODE Server. It doesn't work, or it does and then it doesn't. Just install it as a separate docker container (very easy) and connect it in Nextcloud.

• OnlyOffice might look or even function better, but getting it to run and store locally is either expensive or impossible (to me).

• It works fine in a docker container on a VM in Proxmox (on a NUC i3 cpu (2 allocated to the VM), 32 Gb ram, 8Gb allocated to the VM)

Simple steps:

• Install nextcloud in a docker container:

version: '2'
volumes:
 nextcloud:
 db:
services:
 db:
   image: mariadb:10.6
   restart: always
   command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
   volumes:
     - db:/var/lib/mysql
   environment:
     - MYSQL_ROOT_PASSWORD=password
     - MYSQL_PASSWORD=password
     - MYSQL_DATABASE=nextcloud
     - MYSQL_USER=nextcloud
 app:
   image: nextcloud
   restart: always
   ports:
     - 8080:80
   links:
     - db
   volumes:
     - nextcloud:/var/www/html
     - /mnt/data/nextcloud:/var/www/html/data #store all the files on the NAS
     - /home/docker/nextcloud/config:/var/www/html/config #easy editing of config.php for trusted domains (tailscale)
   environment:
     - MYSQL_PASSWORD=password
     - MYSQL_DATABASE=nextcloud
     - MYSQL_USER=nextcloud
     - MYSQL_HOST=db

Files will be stored on the NAS: /mnt/data/nextcloud/<username>/files

• Install Collabora (putting this in a docker compose file didn't work):

docker run -t -d -p 9980:9980 -e "extra_params=--o:ssl.enable=false" collabora/code

• Add/enable the app Nextcloud Office in Nextcloud

• Connect the Collabora server (IP-address:9980) to it in the administration settings -> Office.

• Edit config/config.php and add the tailscale IP-address of the machine you've installed everything on.

'trusted_domains' =>
  array (
    0 => '192.168.178.241:8080',
    1 => 'tail.scale.ip.address:8080',
  ),

• Test and drink wine if it (finally) works.

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.

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?

Has anyone installed NextCloud on Proxmox for the private cloud?

According to the NextCloud website, the server portion runs on Docker. Then I found a how-to that says to set up a Proxmox container and install Docker/Portainer first.

Is there no way to create a Proxmox VM with a Ubuntu server and then install NextCloud?

Currently getting into using Nextcloud for my own personal use but am learning about other open source cloud solutions like Proxmox and OpenStack. However I am getting confused by the terminologies and how they all relate to each other. They're advertised as IaaS's but I see some people deploy Nextcloud on top of another, say Proxmox. So as I understand it, I can either run Nextcloud directly on the bare metal, on top of the OS, or I can use something like Proxmox/OpenStack to containerize or create VMs of Nextcloud to run on top of my server? If I were to do the latter, what are some pros/cons of it?

very new to Proxmox and hypervisor's in general, but I have a Xeon 12-core machine here with 64gb mem and 30Tb of external storage hooked up via Thunderbolt connection, and 5 static ip's to play with... I would like to come up with a logical, sane plan to provide nextCloud, openOffice, email server with webmail, some sort of monitoring software or dashboard?

I will admit, I feel I am lacking a good understanding of how virtual servers, containers, appliances should be arranged in a given environment, could any profer a casual description of how you personally would set about deploying nextCloud & openOffice (or another office option?) on a Proxmox box comprised of the bits I mention above? VM, LXC or appliance for nextCloud, separated from open office? Mail server in its own VM, or..? Separate instance as reverse proxy ala Nginx, or no need with real static IPs? Not asking for a line by line tutorial or anything, just some thoughts on best practice in terms of (virtual) topography? thx in advance all..

Currently running nextcloud in a DietPi VM. It takes all the work out of it as far as installing a web server and all of that.

Going to setup a proxmox build on a mini PC and want to do it right the first time. Keep reading about Docker but it is a bit of a mystery at this point. Was thinking linux container in proxmox but not sure what else would be needed to get it running.

Hey there. It's a topic that's been discussed many times and it seems as though there are varying opinions. I've come up with a few options and wanted to get the community's input. Looking primarily for easy of use and simplicity of maintenance. Would prefer automatic updates and easy backup/restore.

1. Official AIO using Portainer via Docker Compose - Leaning towards this option as it's "official" and doesn't use sqlite3, from what I understand. I see sqlite3 is not recommended when using sync from multiple users. Plus backup/restore should be easy?

2. Tteck Nextclound TurnKey VM - Like this option for more isolation, but not sure if adding a "third-party" of TurnKey is preferred? Adds a layer of mild complexity and you're then dependant on TurnKey for updates and continued support.

3. Tteck NextcloudPi LXC - Seems like the easiest solution, but not sure if the Pi version is much different from the full/official version?

4. Create an Ubuntu/Debian LXC and, during OS installation, select to install Nextcloud - Tried this once. Seemed ok?

5. Download Nextcloud LXC template directly from Proxmox's Template function - Seems like a similar option to Tteck's VM solution from option #2, as it says TurnKey?

6. Other solutions?

Any insight is greatly appreciate! Thanks in advance.

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!

Well I am new, to Proxmox and Nextcloud. I know of Nextcloud and will be building myself a Proxmox server for home. In the meantime I have a Proxmox server to tinker with thats not owned by me.

In anycase, I was wondering for those Using both, how are you deploying it at home? Are you using a VM or container? OS with Nextcloud installed on top or a pre-built Nextcloud image/template? What else did you need to install to get it up and working?

Ideally, I would be interested in: Nextcloud + Nginx (reverse proxy? + HTTPS) as I am comfortable with Nginx. Database I guess would depend on the Distro behind Nextcloud (I prefer CentOS if I can use SEL like in a VM, Debian/Ubuntu if it is a container)

Looking to get an idea of how people are setting this up, Thanks

I really want to give it another go to replace Microsoft 365 and be data sovereign. I'm technical enough to self-host and support via the team. What I'm not good at is finding best practice guides. For example;

- user lifecycle management? Where is that handled such that our users only have one set of credentials? Nextcloud?, Mailserver?, Keycloak or alternatives?
- email server? I'm familiar with Mailcow and how to host without spam, but how does that integrate, and again during user provisioning? And what about shared mailboxes, groups, delegations, aliases etc...I mean it says they have Nexcloud Groupware, but what is the server behind it then? What is best practice?
- Likewise with NextCloud Talk and NextCloud Office

Perhaps I am overthinking this, but to me it seems that the mail server is super important to glue things together and help with communication, but that is the part that isn't included. And pointers towards best practice?

Hey everyone,
I’m part of an internal working group at a healthcare provider with around 9,000 employees (roughly 500 of them in non-medical administration), and we’re currently having some pretty serious discussions about whether we could replace Microsoft 365 entirely with Nextcloud.
More specifically, we’re looking at:
Nextcloud Talk instead of Teams
Collabora or OnlyOffice instead of Word/Excel/PowerPoint
possibly Nextcloud Mail for internal communication instead of Outlook/Exchange
The main driver is honestly cost. The M365 licenses alone for our administrative staff add up to a significant amount every year. On top of that, GDPR and general data protection concerns are a major factor — especially in healthcare, where US-based cloud services tend to be viewed much more critically.
I’d really be interested to hear if anyone here has gone through a similar transition and could share some real-world experience.
Especially:
Has anyone actually replaced M365 completely with Nextcloud? How did it go?
Is Nextcloud Talk realistically usable as a day-to-day Teams replacement, or do you run into limitations quickly?
How well do Collabora or OnlyOffice work as substitutes for Word/Excel in practice? Where are the real pain points?
How did you handle user adoption? Telling people “we’re taking away Teams and Outlook” usually doesn’t go over particularly well 😅
Are there any healthcare-specific pitfalls we should be aware of? For example integrations with clinical systems, scheduling/on-call tools, and similar things?
We’re still very much in the early discussion phase, so honest opinions — including “don’t do it” experiences — are absolutely welcome.
Thanks in advance!

Hi all,

A general question and probably something of an opinion. I've recently started using NextCloud, it's currently installed on my TrueNAS Scale box, a DIY NAS. I have a second box which runs Proxmox to run services.

I am debating moving my NextCloud app over to Proxmox, my main reasons for this is my backup solution. I run Proxmox Backup Server which automatically backs up my VMs and LXCs, I don't get this functionality in TrueNAS Scale. I should have the space to run the VM on Proxmox and have begun looking into it.

Just looking for opinions if this is worth making the switch now, while I'm only two weeks into running NextCloud from TrueNAS or Proxmox.

Thanks all :)

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.

Sorry mostly a rant but also want to know if anyone else has gone through this.

Why do so many providers of large code base systems seem to have the ugliest kludged together docker support possible, breaking the whole ethos of docker one way or another, bunging it all in a single image, requiring things be named specifically or a volume mapped with a specific name (NextCloud AIO) or requiring the host OS have specific stuff installed (OnlyOffice) !?

Trying to migrate my OnlyOffice install from a bare metal server that ran docker into an LXC on my Proxmox box but apparently because the host doesn't have systemd then it won't work, I think it might be that it's unprivileged so doesn't have access to systemd. Surely needing systemd on the host breaks the whole point of docker making small containers that have repeatable results on different systems.

I'm guessing my only option is to create a VM instead of an LXC but I'd prefer an LXC as the VM will consume all the ram assigned for the read cache, which in a single OS isn't an issue but I run some AI Inferencing and the VM won't give that memory back to another VM/LXC I don't think.