my connection has disabled for security reasons


My connection is disabled for security reasons from a digital ocean, they opened a ticket for this issue and said; “you need to resolve this problem reply to this ticket”. So I have done this and sent reply one week ago, nobody answers, I also opened a new ticket but nobody answers again, I can’t reach anybody at the digital ocean, what should I do? is there any other mail address for the digital ocean?


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hey friend,

It looks like our team was able to respond and get that re-enabled.

In case someone comes here for the same reason later, I do want to expand a bit on the potential for resolving these situations faster. I want to make sure that everyone knows what options they have available. For that reason, what I’m about to say is not necessarily to you, but to future readers.

In an event in which your server has been compromised and used to attack others on the internet, our top priority will be disabling that to prevent outages that stretch multiple customers, and to protect the internet as a whole. Reading your response to that situation, and re-enabling network will be secondary priorities. Your fastest and most reliable resolution will be to resolve the issue by creating a new droplet. This is just an example of how your workflow could go:

  1. Snapshot impacted droplet.
  2. Create new droplet from snapshot.
  3. Log in and instantly kill outbound traffic in the droplet’s firewall.
  4. Investigate the cause of the problem.
  5. Clean up the server.
  6. Re-enable your outbound traffic in the droplet’s firewall.
  7. Change your DNS to the new IP.
  8. Destroy the droplet, or if locked inform our team that you are ready to destroy the droplet.

While you can wait for us to re-enable networking, we provide a wealth of resources designed to help you get back on your feet without our intervention. Ideally we never enter into this situation anyway, but we understand that you might not be aware of vulnerabilities in the software that your droplet runs. We also understand that new vulnerabilities are discovered in software every day, and that sometimes these situations occur before you can reasonably be aware of it. We mean you no harm, we simply want to protect you and other customers from harm, and so we disable the networking to keep you safe.

After all, the data on that droplet could be of incredible value to you. If your droplet has been compromised, the protection of that data is extremely vital.