Private Network address in console does not match physical machine

I have 3 droplets in the same region and VPC. I cannot access 1 of them from any of the other 2. Private networking is enabled on all. The 1 droplet giving issues displays one IP address in the console but on the droplet eth1 is an entirely different address in a complete different subnet. How do I fix this?

Submit an answer

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!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


This is quite strange, was the Droplet created before 1 October 2020 and did you manually have to place it into a VPC network as described here?

Regards, Bobby