Issue with domain verification during Nextcloud AIO setup in Docker

I want to show you a relatively easy approach to address the issues you’ve run into.

With NGINX Proxy Manager (NPM), you can host virtually any domain or subdomain within your LAN, as long as the devices share the same IP address range, and without needing to create any special new network ranges or VLANs.
You also don’t have to modify your external network setup—everything stays simple inside your local infrastructure.

My setup:
I personally run 5 virtual machines (VMs) on Proxmox at home, hosting a wide range of self-hosted services in Docker, including Nextcloud AIO, Paperless-ngx, Rocket.Chat, Mattermost, MeshCentral, and more. Everything is routed through NGINX Proxy Manager, and it all works flawlessly.

Proof that NGINX Proxy Manager handles large Nextcloud file syncs well:
→ My forum post: Testing large file synchronization (23.7 GB) with Nextcloud AIO and NGINX Proxy Manager

Additional benefits of using NGINX Proxy Manager:

  • :green_circle: Easy SSL certificate management via Let’s Encrypt (including wildcard support)
  • :green_circle: Automatic certificate renewal
  • :green_circle: Simple web UI for managing all domains, subdomains, ports, and rules
  • :green_circle: Supports IP allow/block lists, HTTP authentication, and rate limiting
  • :green_circle: Fully Dockerized – easy to back up, migrate, or restart

NGINX Proxy Manager is an excellent solution for anyone running multiple self-hosted services and looking for a clean, centralized way to manage access within their LAN or from the internet.

1 Like