Presne tak — to bola nelogická formulácia. Ak bežà reverzný proxy, porty 80 a 443 idú na proxy, nie priamo na hosta s Nextcloudom.
Hi,
Nextcloud isn’t a peer-to-peer platform.
It’s a centralized server — one main installation that manages all users, files, and apps.
Everyone connects to this single instance through a web browser or the official Nextcloud client.
Clients only sync data; they don’t host or share anything themselves.
If you want your team to work remotely, you’ll need one properly configured and reachable server.
There are two basic setup options:
Direct setup (no proxy)
If you’re only running Nextcloud and nothing else on that host:
-
buy a cheap domain (5–10 €/year) and point it to your public IP (DNS A record),
-
forward ports 80 and 443 on your router directly to the machine running Nextcloud AIO,
-
during setup, use that domain — AIO will handle HTTPS automatically.
With reverse proxy
If you plan to host multiple services (for example Nextcloud, Jellyfin, Portainer, Plex, etc.),
then you should put Nextcloud AIO behind a reverse proxy such as NGINX Proxy Manager, Caddy or Traefik.
In that case:
-
forward ports 80 and 443 from your router to the proxy server,
-
and let the proxy route traffic internally to the AIO instance.
Avoid using Cloudflare or other CDN-based tunnels — they often cause problems with large uploads and Talk connections.
You can install AIO directly on Linux or run it inside a Proxmox VM for better isolation, snapshots, and easy rollback.
A single NVMe drive is perfectly fine — just make sure the host is stable and has enough resources for Docker containers.
Once it’s up, simply create user accounts in the admin panel — your teammates connect securely via your domain and start collaborating right away.
—
TIPS
My setup walkthrough Proxmox + NGINX + Nextcloud AIO + Watchtower Deployment
Settings VM for the large files upload