Missing private IP in a digitalocean droplet? We can help you.

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Service.

Let’s take a look at how our Support Team help a customer  deal with this digitalocean error.

Missing private IP in a digitalocean droplet

DigitalOcean Droplets are Linux-based virtual machines (VMs) that run on top of virtualized hardware.

Each Droplet you create is a new server you can use, either standalone or as part of a larger, cloud-based infrastructure.

You can use it on any services provided by DigitalOcean, for example all Droplet plans, Spaces object storage, Block Storage, and Load Balancers.

NOTE: We offer this Free Trial to help make building amazing things on DigitalOcean as easy and accessible as possible.

Today, let us see the steps followed by our Support techs to resolve it:

1.Firstly, find private IP from digital ocean portal

2.Then, run the below command

lshw -class network

3.Command to find name and mac address of private IP interface as below

root@sta01:~# lshw -class network
USB
*-network:0
description: Ethernet controller
product: Virtio network device
vendor: Red Hat, Inc.
physical id: 3
bus info: pci@0000:00:03.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: msix bus_master cap_list
configuration: driver=virtio-pci latency=0
resources: irq:10 ioport:c0c0(size=32) memory:fd012000-fd012fff
*-virtio0
description: Ethernet interface
physical id: 0
bus info: virtio@0
logical name: eth0
serial: 6e:1e:e1:76:13:78
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=virtio_net driverversion=1.0.0 ip=64.225.28.44 link=yes multicast=yes
*-network:1
description: Ethernet controller
product: Virtio network device
vendor: Red Hat, Inc.
physical id: 4
bus info: pci@0000:00:04.0
version: 00
width: 32 bits
clock: 33MHz
capabilities: msix bus_master cap_list
configuration: driver=virtio-pci latency=0
resources: irq:11 ioport:c0e0(size=32) memory:fd013000-fd013fff
*-virtio1 DISABLED
description: Ethernet interface
physical id: 0
bus info: virtio@1
logical name: eth1
serial: 36:0a:f0:09:a5:ef
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=virtio_net driverversion=1.0.0 link=no multicast=yes
root@sta01:~#

4.Now, we need to create a section as below in /etc/netplan/50-cloud-init.yaml

eth1:
addresses:
- private_ip_here/16
match:
macaddress: mac_address_here
nameservers:
addresses:
- 67.207.67.2
- 67.207.67.3
search: []
set-name: eth1

5.Finally, reboot server.

[Need a solution to another query? We are just a click away.]

Conclusion

Today, we saw steps followed by our Support Engineers to resolve Missing IP in a digitalocean droplet