My resource is attached to a Private Network but has no IP address on the network
When you attach a resource to a Private Network, the Private Network's built-in DHCP defines an IPv4 and IPv6 address for the resource on that network. This is managed via Scaleway's internal IPAM.
- Find out how to attach a resource to a Private Network
- Find out how to view your resource's IP address on the Private Network
- Find out how to specify the IP address to use when attaching a resource
- Find out how to run connectivity tests to diagnose connectivity problems
IP addresses are allocated asynchronously from the attachment of the resource in most cases. The IP will therefore not be immediately returned upon attaching a resource via the API, and there may be a brief delay before it displays in the console, as shown below:
However, in some cases even after waiting, an IP address may not be set for your resource on the Private Network. Read on below to find out more about this problem, and how to solve it.
No IP address is displayed and I have not activated DHCP
You may have attached a resource to an "old" Private Network on which you have not activated DHCP. In this case, no IP address for the resource on the network is configured.
You will need to carry out manual configuration to set the IP address on the resource or activate DHCP.
We strongly recommend that you activate DHCP on the Private Network to let us automatically handle IP address management.
Read our dedicated documentation about VPC migration for more information about how "old" Private Networks are migrated to the VPC, including DHCP activation.
No IP address is displayed but I have activated DHCP
This may be because the resource was attached to the Private Network some time ago before the product was integrated with IPAM. Therefore, no address is reserved with the IPAM for the resource on this Private Network.
To fix this problem, detach your resource from the Private Network, and reattach it.
Elastic Metal servers
Note that some manual configuration of the network interface is required for Elastic Metal servers. Follow the steps in our dedicated documentation.
You can also attach custom resources, such as virtual machines hosted on your Elastic Metal server, to Private Networks, by specifying their MAC addresses upon attachment/ Follow the instructions for attaching such a resource in the Private Networks documentation.
ArchLinux and Debian Bullseye
DHCP should work out of the box for attached resources running any and all Linux distributions. However, when it comes to ArchLinux, we are aware of a problem when it comes to setting a Classless Static Route to our service IP address 169.254.169.254.
In this case, if you are using systemd-networkd and do not have a route to our service IP address 169.254.169.254, you should try updating and upgrading the packages on your system.
There is also a known bug affecting Debian Bullseye, that prevents DHCP clients from correctly applying the default route. For this specific bug, we recommend using another distribution, such as Debian Bookworm.