A small knowledge for Windows NC 28 AIO Nginx Proxy Manager Homelab

[romi1996]

Hi, I'm a noob that is very new for docker and NC Wordpress stuff few days ago, inspired by the NC, NPM, WP community knowledge.
My original idea is to host NC and Wordpress through a reverse proxy. However, since setting up proxy for NC28 is tiring enough and my case is one of the weird ones that I'd like to share. I have not finished WP yet because it is still having problem with SSL with NPM and providing the current guide for WP will out of NC scope of discussion.

System environment:
Intel Xeon, Windows 10 Pro x64, Docker Desktop WSL 2, DDNS

Steps to reproduce (Clean install only):
0. A working ddns name.

1. Install Docker Desktop: Here and run with Administrated Privilege (I would not recommend toying with elevated privilege, please consider well after this).
2. Deploy the necessary extensions in Docker Desktop UI for debugging and visualization: Port Navigator
3. Beginning to install NC Master Container: Open CMD in Administrated Privilege (Again, I would not recommend toying with elevated privilege except for noobs like me, but anyway, please consider well after this).

#--env APACHE_IP_BINDING=172.18.0.2 ^ //Dear Devs, I don't know if I do it right, but this can sure crash Apache Container, even for 127.0.0.1
docker run ^
--init ^
--sig-proxy=false ^
--name nextcloud-aio-mastercontainer ^
--restart always ^
--publish 8080:8080 ^
--env APACHE_PORT=11000 ^
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config ^
--volume //var/run/docker.sock:/var/run/docker.sock:ro ^
--env SKIP_DOMAIN_VALIDATION=true ^
#--env NEXTCLOUD_DATADIR="/run/desktop/mnt/host/" ^
#--env NEXTCLOUD_MOUNT="/run/desktop/mnt/host/" ^
--env NEXTCLOUD_ENABLE_DRI_DEVICE=true ^
nextcloud/all-in-one:latest

4. Access localhost:8080 or 127.0.0.1:8080 and install normally [NC 28]
5. When installed, prepare the Nginx Proxy Manager docker-compose.yaml, run it with cmd elevated command docker-compose up -d at same location with the file.

version: '3.8'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    networks:
      - default
      - wordpress_app-network

6. Manual routing traffic.

• In Docker Desktop, open PortNavigator Extension
• Before continuing, for newcomers, you must take your time to have a look and know how to use this extension. The key is to understand how to manually connect a container to a network.
• Connect the nginx container to the nextcloud network

7. You will see the nginx pop up at nextcloud network, and it will show as 14 containers running. Now is the time to get what you need to proxy correctly. In the Nextcloud network, you will have to look for the Nextcloud Apache Container IP and it's exposed port.
8. In this step, you must use the correct Apache IP and it's port for forward host name/ip and port, this setting is not the same with NC Guide where it usually being 127.0.0.1 and localhost.

• Now, it's the time for setting NPM by accessing localhost:81 and follow instruction from Here
• Setup host proxy for NC 28, create a new host proxy. Based on NC Reverse Proxy Guide of NC Team for NPM
  
  
  Advanced tab:

client_body_buffer_size 512k;
proxy_read_timeout 86400s;
client_max_body_size 0;

9. Finished
   Final words: This is the exact reproduction steps for my case. I hope this post will benefit someone. Further discussion is welcome. thank you!