Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Private Networking between 2 droplets isn't working out-of-the-box in NYC3
I’ve recently set up a new droplet in NYC3, and I’m trying to have a Django setup on my first Droplet with PostgreSQL on another one on NYC3 that I’ve had set up for a while, and linking them with private networking. I haven’t been met with much success, though. I have set up the networking interface to the point where it shows up in ifconfig on the first droplet, but the new droplet had private networking on when I created it, and initially, trying to do a connection of any kind (I have attempted ssh, ping and Django) has not worked at all, it would act like the other machine was firewalled out and would time out. On both of them, I can connect to themselves with the private IP, I just can’t get them both to connect with the private IP. I can even connect to them with the public IP and that minimally works but I want to get private networking set up.
I’m not sure if this problem has to do with firewalls. I do have Cloud Firewalls enabled on my first droplet, but I don’t on the second one, but nothing changes anything as far as I’ve tried. I have not attempted to change any iptables settings, but I have also tried starting up another droplet and having it connect to the new one and vice versa, and it has not worked, so I’m puzzled to why it’s not working because I have had this issue for more than a day already.
Anything would help to get this working, thanks.
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.×