Is DigitalOcean blocking inbound traffic to customer droplets?

  • Posted August 13, 2013


I am attempting to monitor a recently created droplet from my enterprise network monitoring solution and have been unable to successfully connect to my droplet via SNMP. I’m monitoring hundreds of other servers and devices with this tool, so I’m confident SNMP communications are failing somewhere between my corporate network and the DigitalOcean network. The local host-based firewall is properly configured to allow SNMP and snmpd is configured to access connections accordingly, but I am still not able to connect. Is it possible that this traffic is being blocked at the DigitalOcean network edge?

Thanks! Brad


Submit an 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.

@rich: That post it from 2012 – we no longer offer free trials and as a result of that we do not block SMTP by default anymore. <br> <br>This article says DigitalOcean DOES block 25 unless a request is made to unblock it. <br> <br>Please clarify because I’ve been chasing my tail for 2 hours trying to figure out why I cannot even telnet to 25. <br> <br>Thanks.

We do not block any ports by default. Try telnet-ing to the SNMP port on your droplet from your corporate network – does that work?