11 hours ago, Ofir aviel said:
It's a virtual network on digitalocean
Ah, then it makes a tad more sense that a simple fix like this won't work.
I'm not quite familiar with DO, but I'll try to come with some possible solutions, based on available information:
Maybe checking out this post?
Most often when receiving reports of this, the case is that at least one droplet has had private networking enabled after it’s creation, but it has not been set up yet in the operating system. If that might be the case for you, try these instructions:
You will also want to make sure that the droplets are both on the same account, as private networking will be limited in communication to droplets on that same account.
Other than that:
Is the address range of the VPC the same as the server IP-ranges?
And is the firewall setup of the VPC made to allow all local communication?
and remember to reboot after changes on the VPC and/or droplet configuration.