Files

defiQUG dbd517b279 Sync workspace: config, docs, scripts, CI, operator rules, and submodule pointers.

- Update dbis_core, cross-chain-pmm-lps, explorer-monorepo, metamask-integration, pr-workspace/chains
- Omit embedded publish git dirs and empty placeholders from index

Made-with: Cursor

2026-04-12 06:12:20 -07:00

3.2 KiB

Raw Blame History

NPMplus: Verify Running, IP, and Gateway

Last Updated: 2026-02-05
VMID: 10233
Host: r630-01 (192.168.11.11)

Expected configuration

Item	Value	Source
Gateway	192.168.11.1	`config/ip-addresses.conf` (`NETWORK_GATEWAY`); UDM Pro / LAN
Primary IP (eth0)	192.168.11.166	`IP_NPMPLUS_ETH0`; docs (NPMPLUS_HA_SETUP_GUIDE, NPMPLUS_SERVICE_MAPPING)
IP used by UDM Pro	192.168.11.167	Port forward 76.53.10.36:80/443 → 192.168.11.167:80/443
Admin UI	Port 81 (HTTP)	https://192.168.11.166:81 or https://192.168.11.167:81

NPMplus can have one or two addresses (.166 and .167); UDM Pro must forward to .167 for public access.

Verification script

From the repo (requires SSH to r630-01):

# Copy and run on Proxmox host
ssh root@192.168.11.11 'bash -s' < scripts/verify/verify-npmplus-running-and-network.sh

Or from a machine that has the repo and can SSH to r630-01, use the run-via-proxmox-ssh pattern: copy the script to the host and run it there.

On the Proxmox host directly:

# If you are already on r630-01
bash /path/to/verify-npmplus-running-and-network.sh

The script checks:

Running – pct status 10233 is "running"
IP(s) – container has at least one of 192.168.11.166, 192.168.11.167
Gateway – default route is 192.168.11.1
Admin UI – port 81 responds inside the container

If the container is stopped or IP/gateway wrong

Fix IP and gateway, then start (recommended):

# From repo (copies and runs on r630-01)
ssh root@192.168.11.11 'bash -s' < scripts/npmplus/fix-npmplus-ip-and-gateway.sh

This restores the correct gateway 192.168.11.1 and preserves the documented dual-address layout when present:

eth0 = 192.168.11.166/24
eth1 = 192.168.11.167/24 with the default gateway

If the container only has a single interface, it falls back to eth0 = 192.168.11.167/24, gw = 192.168.11.1.

Or start only:

ssh root@192.168.11.11 "pct start 10233"

Wait ~30 seconds for NPMplus (Docker) to start, then run the verification script again.

If IP or gateway is wrong

Correct the container network (run on r630-01). Example for single interface with .167 (UDM Pro):

pct set 10233 -net0 name=eth0,bridge=vmbr0,ip=192.168.11.167/24,gw=192.168.11.1
pct stop 10233
pct start 10233

Example for two interfaces (.166 and .167) if your setup uses both:

# Keep .166 on eth0, put the default gateway only on eth1 / .167
pct set 10233 -net0 name=eth0,bridge=vmbr0,ip=192.168.11.166/24
pct set 10233 -net1 name=eth1,bridge=vmbr0,ip=192.168.11.167/24,gw=192.168.11.1
pct stop 10233
pct start 10233

After changes, re-run the verification script and confirm UDM Pro port forwarding still points to 192.168.11.167.

Quick reference

Check	Command (on r630-01)
Status	`pct status 10233`
Network config	`pct config 10233 \| grep net`
IPs inside CT	`pct exec 10233 -- ip -4 addr show`
Gateway inside CT	`pct exec 10233 -- ip route show default`
Admin UI (local)	`pct exec 10233 -- curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:81`

3.2 KiB Raw Blame History Unescape Escape