Operating system and version (e.g., Ubuntu 24.04):
Debian 12
Web server and version (e.g, Apache 2.4.25):
Apache 2
Reverse proxy and version _(e.g. nginx 1.27.2)
Squid Proxy
PHP version (e.g, 8.3):
8.2.x
Is this the first time you’ve seen this error? (Yes / No):
no
When did this problem seem to first start?
in the past
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Bare Metal / Linux Container
Are you using CloudfIare, mod_security, or similar? (Yes / No)
Pangolin in the future
Feature request for Nextcloud & High-Performance Backend (Signal Server):
Hello guys,
this is my first post and i would like to address a feature request, which might be useful for a very large community out there.
I would like the Nextcloud Dev Team to release a fully configured Linux Container with Nextcloud, and another one with the High-Performance Backend (coTurn Server) for the use in Proxmox and other Hyper-Visor´s. Not everybody wants a docker deployment as an additional virtualisation. I myself don´t see the the benefit of this, but that might be my problem at all…
There are so many Proxmox HomeLab users and professional users out there and i would be very useful to have an “out-of-the-box” LXC, which can be implemented in Proxmox and to deploy a clean Nextcloud instance with the LAMP stack for example and all necessary packages and pre-configured php.ini for the best production deployment. I would also recommend to install the php database drivers for mariadb and postgres, so the admin has the chioce to select the database he wants…
There are some templates out there, like TurnKey Linux ( Nextcloud | TurnKey GNU/Linux ) or Proxmox Helper Scripts ( Proxmox VE Helper-Scripts ), but unfortunately they all have some bugs in it… So with a LXC Nextcloud template from the Nextcloud Dev Team itself, we could deploy a Nextcloud instance within minutes. That would be really great to have!
Same goes for the High-Performance backend…
Hope some ppl. will find my feature request useful and might vote for it!
If you’r looking for an official solution, there is already Nextcloud AIO, which should generally work in an LXC, although I would personally recommend a VM for it.
If you absolutely need to use an LXC and don’t want to use Docker, I recommend a manual Nextcloud installation.
While installation scripts can help you to get up and running quickly, they generally fall short when it comes to long-term maintenance, especially with regard to the LAMP stack and the underlying OS. Setting everything up manually gives you a much better understanding of the entire environment, making maintenance easier in the long term.
not a proxmox user myself, I prefer LXD, but the snap works fine in LXC, see SCUBA’s Nextcloud snap server setup & specs… sure the fail-over redundancy is a bit overkill, but really cool
Thank you very much! I saw your script uses docker, which i am not a big fan of. All other LXC on my server run without Docker and i will stick to that.
So, thank you all for providing really helpful informations! The german site from @bb77 is really cool and comes very near to what i am searching for. I will go through all the documentation and will set up a new LXC with that description.
I personally prefer Apache webserver over NGinx, but that´s a minor. As you are experts in setting up a new LXC Nextcloud instances, i would like to ask you some more questions.
It came into my mind to have a set up for Nextcloud like this:
1x LXC with Nextcloud using PHP 8.3, Apache, Redis, Crowdsec, which will be exposed to the Internet
1x LXC with a Postgres DB Server for use with the Nextcloud instance, so to have a separate DB Server and Database, which will be not exposed to the internet and will only be accessable for the Nextcloud instance within the same network
1x LXC for the Nextcloud High-Performance Backend Server
1x LXC for WOPI Collabora (accessable only within network, not exposed to the internet)
1x LXC for Whiteboard Server (accessable only within network, not exposed to the internet)
Then using Proxmox Backup Server for (minimum) daily backups for these Containers.
Having separate LXC for DB Server, WOPI, HPB and Whiteboard Server enables me to reuse these for several other Nextcloud instances (private / enterprise).
Has anybody experiences, if there will be significant performance issues with this setup? I thought about this for maximum reliability, security and restore capacity in case there will be a hacker / bot attack on the exposed Nextcloud instance. So all other LXC, which are not exposed to the internet, would be “safe”. That´s what i had in mind. Really love to hear your thoughts on this.
Just wann say “Thank you” for guiding me to the Carsten Rieger Website and these very useful scripts! I have used the scripts and everything is working like a charm now! Even the documentation for the High-Performance Backend is absolutly stunning! This was exactly, what i have looked for.
I have setup everything within a few hours and haven´t ran into any problems.
Really nice, thank you so much!
