How do I change static networking without losing dedicated-server access?
A static-network change can remove the route carrying your own SSH session. Verify independent console access and the exact provider network values before applying it. Use the active network manager’s supported change/rollback mechanism; mixing NetworkManager, systemd-networkd and unmanaged scripts can produce conflicting persistent state.
Before you start
- Working out-of-band console, exact provider network data and an approved prepared NetworkManager profile.
Instructions
1. Identify the manager and active profile
On a NetworkManager-managed server, inspect active connections and the present route. Other managers require their own supported workflow.
nmcli connection show --active
ip route showRecord the actual profile and interface names. Do not guess a gateway or prefix from another server.
2. Apply only a prepared, reviewed profile
For a supported nmcli version, a checkpoint can restore runtime connectivity when a change is not confirmed. The sample assumes an already-created and validated profile named approved-static-profile.
sudo nmcli device checkpoint enp1s0 -- nmcli connection up "approved-static-profile"Replace both names with verified objects. Confirm success only after testing access from a separate session; a runtime checkpoint is not a substitute for reviewing persistent profile contents.
Check the result
- Independent SSH access, expected routing and application endpoints work, and the persistent profile remains correct after the next planned reboot.
Troubleshooting
- The SSH session drops
- Allow the documented checkpoint behaviour and use the already-tested console; do not issue blind competing changes.
- NetworkManager does not manage the interface
- Use the actual manager’s documented transaction/rollback method, not this command.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.