Report this

What is the reason for this report?

Private Network address in console does not match physical machine

Posted on June 2, 2021

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?



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!

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.

Hello,

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

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.

Dark mode is coming soon.