How do I recover a VPS after a network configuration change?
If a guest network change cuts off SSH, use the provider’s independent console rather than repeatedly changing the client. Confirm the assigned network values and correct the specific guest configuration that caused the loss of access.
Instructions
1. Open the correct authorised console
In Britixo’s VPS Access tab, use the offered console action and verify the server identifier. Keep any temporary console URL or credential private.
2. Inspect the current guest state
Compare the live configuration with the service’s assigned network values and the last approved change.
ip -brief address
ip route
ip -6 routeThese read-only commands show addresses and routes. They do not reveal whether a persistent configuration file will recreate the same state after reboot.
3. Correct the supported configuration source
Use the image’s actual network manager and the exact assigned interface, prefix, gateway and resolver settings. On a supported Netplan image, a reviewed configuration can be tried with a confirmation timeout, but keep the console and verify reversion if confirmation fails.
sudo netplan try --timeout 120This applies the already reviewed Netplan configuration temporarily and requests confirmation. It is not a generic command for non-Netplan guests or a guarantee that every change will revert correctly.
Check the result
- An independent external SSH session works through the intended path.
- The persistent configuration is correct and the console remains available until recovery is verified.
Troubleshooting
- The guest configuration looks correct but access fails
- Check provider-level restrictions, assigned IP state and any null route.
- netplan try times out
- Verify the actual reverted state through the console before attempting another change; do not assume success or rollback from the timeout alone.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.