Root Server - AlmaLinux 9.6 Fresh Install, No Network Connectivity

  • Hi everyone,

    I’m having a serious problem with a new Netcup Root Server. Since I bought it, I can’t get the network working at all.

    • I’ve done 15+ fresh installations of AlmaLinux 9.6 (Minimal) directly from the Netcup SCP.

    • Every time, the installation finishes, but the server is not pingable and has no network access.

    • Only VNC works - SSH or ping on the assigned IP fails.

    • I haven’t changed anything manually, just fresh installs.

    Details from the last reinstall:

    Code
    AlmaLinux 9.6 (Sage Margay) - minimal
    IP Address: xxx.xxx.xxx.xxx

    From VNC, I can see cloud-init errors like this:

    Code
    Error: Failed to download metadata for repo 'appstream':
    Curl error (6): Couldn't resolve host name for https://mirrors.almalinux.org

    So it looks like DNS/networking never comes up after install.

    I opened a ticket with Netcup, but it’s been more than 24 hours without a reply, and I urgently need to move data from another datacenter.

    Has anyone run into this before on a Netcup Root Server? Any suggestions on how I can fix this myself (network config, driver issue, etc.), or should I push Netcup to do a manual OS reinstall?

    I’ve attached a screenshot from VNC showing what happens during the installation.

    Any help would be greatly appreciated.

    • I’ve done 15+ fresh installations of AlmaLinux 9.6 (Minimal) directly from the Netcup SCP.

    • Every time, the installation finishes, but the server is not pingable and has no network access.

    […] and I urgently need to move data from another datacenter.

    If you need to move data urgently, I'd suggest a workaround – temporarily use a LiveCD (e.g., AlmaLinux Live Media) or one of the numerous other images Netcup already offer (which should all work out of the box), boot that, make sure that your environment is secure, and then transfer the data (e.g., using separate Local Block Storage).

    Afterwards, tend to the problem with your AlmaLinux installation (maybe on a second KVM instance). In any case, it's a good idea to create your own custom Rescue/Installation Image locally and use this for a fresh installation in order to ensure that you have complete control over your environments at any given time.

    VServer IOPS Comparison Sheet: https://docs.google.com/spreadsheets/d/1w38zM0Bwbd4VdDCQoi1buo2I-zpwg8e0wVzFGSPh3iE

    4 Mal editiert, zuletzt von m_ueberall (13. September 2025 um 21:37)