bea1903ac9
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
1.4 KiB
1.4 KiB
Dev VM (5700) IP change: 192.168.11.60 → 192.168.11.59
Date: 2026-02
Reason: Resolve IP conflict with VMID 3000 (ML node) at 192.168.11.60.
Repo changes (done)
- config/ip-addresses.conf:
IP_DEV_VM="192.168.11.59" - All docs and scripts referencing Dev VM IP updated to .59.
- NPMplus Fourth proxy script uses
IP_DEV_VMfrom config → gitea.d-bis.org, dev.d-bis.org, codespaces.d-bis.org will forward to 192.168.11.59:3000 after you run the proxy update.
On Proxmox (operator)
If LXC 5700 already exists and is still using 192.168.11.60, reconfigure it to use .59:
-
From Proxmox host (r630-01):
pct set 5700 --net0 name=eth0,bridge=vmbr0,ip=192.168.11.59/24,gw=192.168.11.1 pct reboot 5700 -
Or edit the CT’s network inside the container (e.g. netplan or /etc/network/interfaces) and reboot.
-
Update NPMplus Fourth so proxy hosts point to the new IP:
NPM_PASSWORD=xxx bash scripts/nginx-proxy-manager/update-npmplus-fourth-proxy-hosts.sh(Script reads
IP_DEV_VMfrom config, so no change needed if you sourced config.) -
UDM Pro: If you had port forward 22 → 192.168.11.60, change it to 22 → 192.168.11.59.
E2E
- gitea.d-bis.org, dev.d-bis.org, codespaces.d-bis.org are included in
scripts/verify/verify-end-to-end-routing.sh. - They are expected to resolve to 76.53.10.40 (Fourth NPMplus) and are tested as web (DNS, SSL, HTTPS).