New VPS has no network after automatic provisioning – isn't it supposed to work out of the box?

    • Neu

    Hi everyone,

    I just got a VPS pico G11s (Debian 13) that was provisioned automatically. It boots fine and I can log in through the SCP console, but it has had no network since delivery, on both IPv4 and IPv6.

    - The IP, MAC and default route inside the VM all match what the SCP shows
    - Both gateways are unreachable: ip neigh shows the IPv4 gateway as INCOMPLETE and fe80::1 as FAILED
    - The server can't be reached from outside either
    - A power cycle didn't help, and neither did disabling the SCP firewall

    Is this normal for a newly delivered VPS? Is there something I need to activate, or is this something only support can fix?

    Thanks!

    • Neu

    You could try booting the rescue system and check network connectivity there. Support will ask you to do that anyway. A newly provisioned VPS with a default image should have network access right away. Maybe give it an hour or two, but contact support if it doesn't work then.

    • Neu

    Thanks for the tip. I booted the rescue system and it shows the same problem. Gateway 159.195.124.1 is unreachable ("Destination Host Unreachable"), ip neigh shows it as INCOMPLETE, and fe80::1 is FAILED. The routes are correct. Since it also fails in the rescue system, it doesn't look like an OS issue. I'll contact support now.

    • Neu

    I can confirm the same issue. mrlan and we seem to be in the same datacenter - I have the same gateway IP. I did contact support - however, I haven't received any ticket number as of now (which was over 1 hour ago). As of such I have the feeling said gateway is down - the only way to access this server is via the server control panel using WebVNC.