Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I have an old droplet, which is not part of any VPC networks (those were’t a thing 9 years ago when the droplet was created), and I can successfully access port 80 on it. The iptables rules are there in place, nginx is up&running, so far so good.
However, I wanted to make it part of a VPC network, and since only new droplets can be added to a VPC network, I cloned the old one.
So far so good, however once I booted the cloned droplet, and started running some tests, I noticed I was not able to access port 80 outside of the VPC network. The iptables rules, are the same, nginx is running as expected, basically there configuration is the same as on the old server.
Port 80 is accessible from other droplets in the same VPC network, and port 443 is accessible from anywhere, so it seems that some networking layer above my droplets are rejecting the traffic coming from the outside world.
I don’t have any firewall defined on the DigitalOcean portal, I only have the ones that come with the Ubuntu server.
What could be the problem?
Adams Tech
dc4230bda0b4464dbcf3a811978d84
Tomy Hsieh
Stafford
Henery walt
f16ce05482054d6ebc67b8f2affd06
webmaster
Lakshay Mittal
Chandra Pratap
a85f3d362866415d9342a8cebcc419
mrameezraja
nienienienie