Hi, I just ran through the provisioning of a new Debian 12 VM and it started up with the first network interface being enX0 instead of eth0. This means that the network doesn't come up because the /etc/network/interfaces file that BitFolk creates on a new install uses eth0. A simple: # sed -e 's/eth0/enX0/g' /etc/network/interfaces # ifup enX0 makes it work. So at the moment this is a minor bug in our installer for Debian testing, which we will fix. It doesn't affect Ubuntu because as of 22.04 that doesn't use the same installer (it boots the official Ubuntu Cloud Image). I have not yet tested if upgrades from Debian 11 cause eth0 to rename to enX0 or if they retain the eth0 they were previously using. We knew this was probably coming; the only reason why it hadn't happened sooner is that udev didn't know what a Xen network interface was, so it left it alone. Now, apparently, it does. A lot of VM hosting companies seem to be supplying the net,ifnames=0 kernel command line option, which disables all this network interface renaming and ensures you just have eth0. When we last discussed this subject here, most were in favour of us not doing that so as to be more like a "normal" OS install. So we won't. But you can, if you like. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting