Hey @nuclearatlas ,
I have a very similar setup at home – everything runs on my own Proxmox server (using VMs only) where I host Nextcloud AIO, two websites, and a bunch of other services like Plex, Vaultwarden, Jellyfin, Paperless, Calibre, etc. I dealt with exactly the same situation as you’re describing.
Best solution:
Set up a reverse proxy — I recommend NGINX Proxy Manager (NPM) in Docker with its simple GUI.
Forward ports 80 and 443 on your router to the NPM server.
NPM will handle routing traffic to Nextcloud, your websites, and other services.
NPM takes care of SSL — it obtains and renews Let’s Encrypt certificates automatically, so you don’t need to manage certificates manually.
Website hosting:
I recommend a separate VM/CT for the website — it’s easier to manage and scale. I personally run WordPress on its own VM behind the same NPM, and everything works flawlessly. If it’s a simple website, you could also run it on the same machine as NPM.
Cloudflare:
The best approach is to have your own public IP address — this saves you a lot of trouble and unnecessary debugging and is the best way to avoid Cloudflare altogether. Cloudflare proxy mode (orange cloud) often causes issues when uploading large files to Nextcloud. If you do use Cloudflare, stick to DNS only (grey cloud).
Here’s my detailed testing of large file uploads (Nextcloud AIO + Nginx Proxy + Proxmox ballooning + Ubuntu server):
https://help.nextcloud.com/t/testing-large-file-synchronization-with-nextcloud-aio-and-nginx-proxy-june-2025-update/226681
Find some time and read this topic about using Nextcloud AIO via CT - Is there limitations to installing Nextcloud via CT template on Proxmox - #2 by vawaver
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: