Files
proxmox/docs/04-configuration/NPMPLUS_SERVICE_MAPPING_COMPLETE.md
defiQUG 4f97e27f69
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
MIM4U: nginx install/deploy/backup scripts, rate limit, CSP, docs; submodule pointer; txpool retry script
Made-with: Cursor
2026-02-26 22:35:24 -08:00

119 lines
4.7 KiB
Markdown

# NPMplus Service Mapping - Complete Reference
**Last Updated:** 2026-01-31
**Document Version:** 1.0
**Status:** Active Documentation
---
**Date**: 2026-01-18
**Status**: ✅ Configuration Updated
---
## Summary
NPMplus (VMID 10233 on r630-01) acts as the reverse proxy for all public-facing services. Most backend services run on other hosts, but NPMplus can proxy to them over the internal network.
---
## Running Containers on r630-01
### Infrastructure Services (Not in NPMplus)
| VMID | IP | Hostname | Purpose | Ports |
|------|----|----|---------|-------|
| 100 | 192.168.11.32 | proxmox-mail-gateway | Email gateway | 25, 587, 465 |
| 101 | 192.168.11.33 | proxmox-datacenter-manager | Datacenter management | 8006 |
| 102 | 192.168.11.34 | cloudflared | Cloudflare tunnel | Various |
| 103 | 192.168.11.30 | omada | Omada controller | 8043 |
| 104 | 192.168.11.31 | gitea | Git repository | 80, 443 |
| 105 | 192.168.11.26 | nginxproxymanager | Legacy NPM | 80, 81, 443 |
| 106 | 192.168.11.110 | redis-rpc-translator | Redis | 6379 |
| 107 | 192.168.11.111 | web3signer-rpc-translator | Web3Signer | 9000 |
| 108 | 192.168.11.112 | vault-rpc-translator | Vault | 8200 |
| 130 | 192.168.11.27 | monitoring-1 | Monitoring | 80, 443 |
| **10233** | **192.168.11.166** | **npmplus** | **NPMplus Reverse Proxy** | **80, 81, 443** |
---
## NPMplus Configuration (Current Correct Settings)
All these services can be accessed by NPMplus over the internal network, regardless of which physical host they run on.
### Blockchain Explorer
| Domain | Target | VMID | Host | Notes |
|--------|--------|------|------|-------|
| `explorer.d-bis.org` | 192.168.11.140:4000 | 5000 | r630-02 | Direct route (bypasses nginx) |
### RPC Endpoints
| Domain | Target | VMID | Host | WebSocket |
|--------|--------|------|------|-----------|
| `rpc-http-pub.d-bis.org` | 192.168.11.221:8545 | 2201 | ml110 | ✅ Yes |
| `rpc-ws-pub.d-bis.org` | 192.168.11.221:8546 | 2201 | ml110 | ✅ Yes |
| `rpc-http-prv.d-bis.org` | 192.168.11.211:8545 | 2101 | ml110 | ✅ Yes |
| `rpc-ws-prv.d-bis.org` | 192.168.11.211:8546 | 2101 | ml110 | ✅ Yes |
| `rpc.public-0138.defi-oracle.io` | 192.168.11.240:443 | 2400 | ml110 | ✅ Yes (HTTPS) |
### DBIS Services
| Domain | Target | VMID | Host | Port | Notes |
|--------|--------|------|------|------|-------|
| `dbis-admin.d-bis.org` | 192.168.11.130:80 | 10130 | r630-01 | 80 | Frontend |
| `dbis-api.d-bis.org` | 192.168.11.155:3000 | 10150 | r630-01 | 3000 | API Primary |
| `dbis-api-2.d-bis.org` | 192.168.11.156:3000 | 10151 | r630-01 | 3000 | API Secondary |
| `secure.d-bis.org` | 192.168.11.130:80 | 10130 | r630-01 | 80 | Path-based routing |
**Note**: DBIS containers (10130, 10150, 10151) are currently stopped on r630-01 and need volumes to start.
### MIM4U Services
| Domain | Target | VMID | Host | Port | Notes |
|--------|--------|------|------|------|-------|
| `mim4u.org` | 192.168.11.37:80 | 7810 | r630-02 | 80 | mim-web-1 (frontend) |
| `www.mim4u.org` | 192.168.11.37:80 | 7810 | r630-02 | 80 | mim-web-1 (same backend) |
| `secure.mim4u.org` | 192.168.11.37:80 | 7810 | r630-02 | 80 | mim-web-1 |
| `training.mim4u.org` | 192.168.11.37:80 | 7810 | r630-02 | 80 | mim-web-1 |
**Updated**: MIM4U routes to VMID 7810 (mim-web-1) at 192.168.11.37, not 7811. nginx on 7810 proxies `/api/` to 7811 (192.168.11.36:3001).
---
## Container Status Summary
### r630-01 Status
- **Running**: 11 containers (infrastructure + NPMplus)
- **Stopped**: 31 containers (many missing volumes)
### Services That Need to Start
The following containers failed to start due to missing volumes or configuration:
- DBIS containers (10100-10151) - Missing volumes
- Order services (10000-10092) - Missing volumes
- ML/Oracle services (3000-3003, 3500-3501, 5200) - Missing volumes
---
## Port Conflict Check
### Common Ports Used
| Port | Service | VMID | IP | Status |
|------|---------|------|----|--------|
| 80 | HTTP | Multiple | Various | ✅ OK (different IPs) |
| 443 | HTTPS | Multiple | Various | ✅ OK (different IPs) |
| 3000 | API | 10150, 10151 | 192.168.11.155, .156 | ⏸️ Stopped |
| 4000 | Blockscout | 5000 | 192.168.11.140 | ✅ Running (r630-02) |
| 8545/8546 | RPC | 2101, 2201 | 192.168.11.211, .221 | ✅ Running (ml110) |
| 6379 | Redis | 106 | 192.168.11.110 | ✅ Running |
**No port conflicts detected** - Each service runs on a different IP address.
---
## Next Steps
1.**Configuration Files Updated**: `configure-npmplus-domains.js` has correct settings
2. ⚠️ **NPMplus Update Required**: Browser automation failed, need manual update or API fix
3. ⏸️ **DBIS Services**: Containers need volumes created to start
4. ⏸️ **MIM4U Services**: Verify VMID 7810 exists and is running on r630-02
---
**Last Updated**: 2026-01-18