Self-Hosted Main

Yes absolutely.

version: '3.8'

services:

npm:

image: 'jc21/nginx-proxy-manager:latest'

# sysctls:

# net.core.somaxconn: 4096

restart: unless-stopped

ports:

# These ports are in format :

- '80:80' # Public HTTP Port

- '443:443' # Public HTTPS Port

- '81:81' # Admin Web Port

# Add any other Stream port you want to expose

- '21:21' # FTP21

- '20:20' # FTP20

environment:

# Mysql/Maria connection parameters:

DB_MYSQL_HOST: "db"

DB_MYSQL_PORT: 3306

DB_MYSQL_USER: "npm"

DB_MYSQL_PASSWORD: "npm"

DB_MYSQL_NAME: "npm"

# Uncomment this if IPv6 is not enabled on your host

# DISABLE_IPV6: 'true'

volumes:

- ./data:/data

- ./letsencrypt:/etc/letsencrypt

# - ./logrotate:/etc/logrotate.d

depends_on:

- db

db:

image: 'jc21/mariadb-aria:latest'

restart: unless-stopped

environment:

MYSQL_ROOT_PASSWORD: 'npm'

MYSQL_DATABASE: 'npm'

MYSQL_USER: 'npm'

MYSQL_PASSWORD: 'npm'

volumes:

- ./mysql:/var/lib/mysql

This is pretty much a default NPM install on docker. When you go to the GUI and add a proxy host, just use the IP address or DNS name of the VM on proxmox.

I suggest creating a custom docker bridge network on which you put all your other docker containers that you want to give access to the local network. There are other reasons a custom bridge is preferred, but that's a different subject.

Here is the terminal command that will create a custom docker bridge network named reverse_proxy:

docker network create --opt "encrypted" --scope "local" --driver "bridge" --subnet "172.27.2.0/24" --gateway "172.27.2.254" --attachable "reverse_proxy"

Here's the NXPM docker-compose.yml I'm using that works for this purpose:

version: '3'

networks:
  reverse_proxy:
    external: true

services:
  app:
    image: 'jlesage/nginx-proxy-manager'
    container_name: 'nxpm'
    restart: unless-stopped
    networks:
      - reverse_proxy
    ports:
      - '443:443' # https
      - '80:80'   # http
      - '81:81'   # npxm webui
    volumes:
      - /opt/docker/appdata/nxpm/data:/data
      - /opt/docker/appdata/nxpm/certs:/etc/letsencrypt

Note the two networks: sections, one outside of and one inside the nxpm service stanza.

Once this container is up and running, you should be able to route to any network service on the local area network connected to your docker host by creating a host redirect in the nxpm webui that points to that services lan.ip:port.

Yes it can