How to Host a Nextcloud Sync Server on Windows Server

Host a Nextcloud sync server on Windows Server by running Nextcloud All-in-One (AIO) in a Linux virtual machine. The prebuilt route in this guide imports the official AIO VM into Oracle VirtualBox.

Nextcloud does not support a native Windows server install; it recommends a VM or Docker image on Windows Server. The prebuilt AIO VM is not suitable behind a reverse proxy, so use the AIO Docker image and reverse-proxy guide for that setup. See the official Nextcloud install page for its Windows Server guidance.

What to prepare

Check that your Windows Server release is supported by the current VirtualBox host requirements, and enable hardware virtualization in firmware. Plan storage for the VM, user files, and backups; reserve a stable LAN address for the guest. Remote access also requires a domain you control.

Before exposing the VM, note its age: the official AIO VM index lists a 1.6 GB OVA last modified September 9, 2024, and a README dated 2022. Read the README and verify the guest OS update process; updating AIO containers does not maintain the Linux VM itself.

Install Nextcloud AIO on Windows Server

1. Install VirtualBox

Get the Windows host installer from the official VirtualBox downloads page. Install it and check Oracle’s current manual for support on your exact Server release.

2. Download the AIO virtual appliance

From the official AIO VM directory, download Nextcloud-AIO.ova and readme.md. The OVA is a Linux guest, not a Windows installer; allow room for its virtual disk and future files.

3. Import the OVA

In VirtualBox Manager, choose Home > Import or double-click the OVA. Review its guest OS and resource settings, select a VM folder, and import. Leave enough CPU and memory for Windows Server and its other roles.

4. Put the VM on your LAN

Open the VM’s Settings > Network. Set Adapter 1 to Bridged Adapter and choose the physical interface that reaches your LAN. Bridging gives the guest its own LAN address; reserve that address in your router. NAT requires extra configuration for inbound traffic.

5. Start the VM and find its address

Start the appliance and run hostname -I in its console. Note the guest’s LAN IPv4 address; if you cannot access the console, look for the VM in the router’s DHCP lease list.

6. Open the AIO management page

Visit https://<VM-IP>:8080 from a trusted device. A self-signed certificate warning is expected on this local management page; confirm the IP belongs to your VM. Save the first-run AIO administrator password, then sign in using the IP address, not a domain, on port 8080. Keep this port off the public internet.

7. Configure the domain and network access

Enter your Nextcloud domain, such as cloud.example.com, and complete AIO’s domain check. For remote access, public DNS must point to your public IP. Forward TCP 80 for certificate validation and TCP 443 to the VM; enable TCP and UDP 3478 only if you use Nextcloud Talk. Keep management ports restricted to trusted administrators.

If validation fails, verify public DNS and firewall forwarding. For LAN-only use, follow AIO’s local-instance instructions instead of using a private IP as the Nextcloud domain.

8. Start the containers and finish setup

Apply a mastercontainer update if prompted. Select only the optional components you need, then choose Start containers and wait for setup to finish. Keep the AIO password separate from the initial Nextcloud account credentials.

Open https://cloud.example.com, sign in, create user accounts, and install the official desktop or mobile sync clients. Select folders to synchronize. Configure AIO backups on separate or remote storage and test a restore. Finally, verify that the VM starts after Windows Server reboots.

Security and maintenance notes

• Update Windows Server, VirtualBox, the Linux guest, and AIO containers separately.
• Use unique passwords and restrict AIO management to your admin network.
• Keep a backup copy off the VM’s disk and confirm that restore works.
• If the older OVA does not meet your maintenance needs, use a maintained Linux VM and the current AIO installation guide.

The interface illustrations above are schematic; the exact labels can differ from the bundled VM’s older AIO release. Use the current AIO documentation for any screen that does not match.