Quote from: italeffect on April 21, 2016, 01:12:26 AM

Quote from: TanteStefana2 on April 20, 2016, 11:24:50 PM

Quote from: ddink7 on April 20, 2016, 09:06:42 PM

Quote from: r4vani on April 20, 2016, 08:50:34 PM

Quote from: ddink7 on April 20, 2016, 08:06:00 PM

What the hell? I just got this from one of my masternodes on Vultr:

Quote

Abuse Team Vultr Staff
2016-04-20 15:13:42
We have suspended your VPS due to information we have received indicating that your account is in violation of our Terms of Service/Acceptable Use Policies, the full text of which is available online at the following URLs for your convenience:

TOS - https://www.vultr.com/legal/tos.php
AUP - https://www.vultr.com/legal/use_policy.php
SPAM - https://www.vultr.com/legal/antispam_policy.php

Monitoring showed a large amount of outbound traffic matching an attack profile which triggered suspension.

Our services are self-managed and we do not provide assistance for analyzing your traffic. You can use utilities such as tcpdump to investigate traffic patterns/data.

Please respond as soon as possible with as much detail as you can provide regarding the activity in question and what you intend to do to ensure it does not occur in the future. If the VPS in question is compromised, you may launch a new one at any time.

Instance destruction may occur if we have not heard from you within the next 18 hours.

Thank you for your cooperation.

-- Complaint Response Team --

What the hell are they talking about?

Sorry, NOW YOU FUCKED UP Grin

set limitation for connections

configure a firewall and set 2 ruls

open dash used ports
close all port

I did all that! The crappy thing is I can't log in, since it's suspended, so I can't even try to check the debug.log or anything. Nor can I see my usage graph.

Qwizzie: 1000 GB per month. I've been running MNs for almost two years now with zero problems...it's really bizarre. Plus Vultr basically accuses me of launching an attack? WTF?

Write to them and tell them what you're running, and ask them to reopen your server. They simply profiled you, and are mistaken. If you are not running a tor exit node, and just running a masternode, that does NOT violate their terms of service as far as I can see reading it here.

Possibly hacked and used for a bot net or spam?

Reading through the comments, I'm inclined to guess that perhaps the virtual box was not updated? Running an older sshd or another service? Weak password for the account? Running a masternode per se shouldn't generate such an abusive amount of traffic that it should get flagged by their automated scripts. If so, well then maybe writing to their support can get the problems solved. For whats it's worth, I have two masternodes on Digital Ocean but have never had any problems like this. I hope this gets resolved for you as soon as possible!