By Bruno Buiret
Hello!
I followed the documentation here to create a gateway droplet and I disabled the public interface on my other droplets, behind the gateway.
The problem is the metadata service on 169.254.169.254 isn’t available anymore and I can’t use ip route add 169.254.169.254 via {your-gateway-IP} dev eth0 since the interface is down.
Is there a way to keep both the metadata service and no public interface?
Thanks!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
When you disable the public interface on a droplet, it does result in the loss of access to DigitalOcean’s metadata service. This is because the metadata service relies on the public network interface to communicate with the droplet.
Unfortunately, maintaining both a disabled public interface and access to the metadata service isn’t possible at this time due to the constraints mentioned above. The metadata service can only be reached over the public network interface.
For more information about DigitalOcean’s metadata service, please refer to our docs here:
https://docs.digitalocean.com/products/droplets/resources/metadata
Hope that this helps!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
