There are a lot of non-productive comments on this thread. It's not our place on the forums to lecture someone about their circumstances. We may never know the full reason behind the suspension, but the fact is that @volgot is a paying customer and fellow DO community member right now. By the same token, @volgot: you're not likely to get much help if every response includes a jab at DO. Let's have a reset here: if @volgot stops venting frustration at DO and we stick to advice/suggestions, we can focus on solving the problem. :)
I've never had this issue, but I also would have expected creating a new droplet from your snapshot to work. That's probably worth retrying, but do it while your current broken droplet is running so you're sure to get a new IP. When you tried/retry that, how are you trying to connect to the new droplet? For example, are you using a browser to access http://newip ?
Something that wasn't clear to me from the problem description: are you having trouble with both inbound and outbound connections? You mentioned HTTP wasn't working, but did you mean inbound HTTP requests to your web server and/or outbound HTTP requests using a tool like curl? What are you doing to test inbound/outbound connections and what are the results of each?
Past that, as was stated above, you'll need to troubleshoot the network connection. Perform a fresh reboot before starting these steps, because you wouldn't want commands you've already ran post-boot to affect the output, get a resolution, and then reboot into the same issue again.
Please paste the output of the following commands so we have some basic details to start with:
netstat -an | grep -i listen
Can you perform DNS lookups and pings? Show us the output from:
ping -c 1 www.google.com
What's in these files?
Is the problem resolved by shutting down your firewall? If you're using pf, shut it down and try in/out connections again:
service pf stop
If you're not able to resolve this issue, are you going to lose files/data? In thinking of what you could do if you're not able to resolve it: Would it be possible to add a block storage device to the broken droplet, copy your files to it, and then connect that block storage device to a fresh droplet to get your files? I've never used DO's block storage feature, so I don't know if that would work or not.