Err I usually disable auto network reset on power cycle . But for your vps, that might have not been the case 
Pm me the main IP And I will disable that option.
You can also make some files immutable so it won’t change 
1 Like
New knowledge today! I didn’t know VPS reconfigure the network on boot.
Fortunately the host was empty yet.
What’s the plural for VPS?
They don’t. It’s an option. Solusvm has a network reset button and virtualizor has an admin level config per vm.
I usually ensure that it is disabled upon creation but I guess one of the guys at the back end enabled it when they were assigning the additional IP and never disabled it back :(.
My bad dude.
Virtual Private Servers, so VPSs?
1 Like
Something weird happens, but not actually a problem.
The first time I installed the server, I configured guests to use a static route (route-eth0 file) like @Mr_Tom suggested . VMs won’t connect to Internet if they don’t have that config.
Yesterday I reinstalled one of the guests and suddenly it does not need the static route configuration. I’ve noticed the same happens in another Proxmox node: some VMs need the static route, others don’t.
I even rebooted the host.
I’ve found if you’re using an additional subnet, with IP forwarding enabled often you don’t need to configure the /32 as an individual route - if that makes sense.
This thread should be saved in the Proxmox museum.
1 Like