Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,048
  • Joined

  • Last visited

  • Days Won

    617

Everything posted by wolstech

  1. OK, you've been suspended. Please let us know when you're ready to work on this and we can unsuspend it for you I've also pushed your login date to the end of December so your account's last login won't go stale while suspended.
  2. That's a piracy site, so it is copyright infringement and will get you suspended. Don't bother moving that here (or to any other USA-based web host for that matter). Don't worry about wasting our time. We'd rather you ask and go elsewhere rather than see you get upset when you spend the time moving it only to get suspended later. You can delete your account at http://www.heliohost.org/classic/support/scripts/delete
  3. You were blocked for failed cPanel logins. Log in using https://heliohost.org/login/ to prevent that from happening. Unblocked.
  4. Was it the offline content that you flushed? Or did you delete your browser's profile?
  5. You're suspended because we received an abuse report for your account. From what I can tell, your welcome emails are not welcomed by spam filters (pardon the pun). Since Yandex censors their reports, it's impossible to know which user flagged it as spam to cause this report to be generated. My recommendation would be to either stop sending welcome emails to your users, or develop better emails that don't get flagged as spam. Tools like https://www.mail-tester.com/ may help with reducing the spam score on your emails. Unsuspended. Please fix the issue within 24 hours. We have received a complaint about your account. Please investigate and fix within 24 hours. Hurricane Electric Abuse Department support@he.net From fblbounces@senderscore.net Tue Dec 5 01:32:26 2017 Return-Path: <fblbounces@senderscore.net> X-Original-To: report@abuse.he.net Delivered-To: report@abuse.he.net Received: from he.net (he.net [216.218.186.2]) by abuse.he.net (Postfix) with ESMTPS id 1809B541058 for <report@abuse.he.net>; Tue, 5 Dec 2017 01:32:26 -0800 (PST) Received: from mrfbl02-den.returnpath.net ([66.45.29.177]) by he.net with ESMTPS (ECDHE-RSA-AES256-GCM-SHA384:TLSv1.2:Kx=ECDH:Au=RSA:Enc=AESGCM(256):Mac=AEAD) for <abuse@he.net>; Tue, 5 Dec 2017 01:32:43 -0800 Received: from poma01.lan.returnpath.net (poma01.lan.returnpath.net [10.2.0.106]) by mrfbl02-den.returnpath.net (Postfix) with ESMTP id 396CB4A0966 for <abuse@he.net>; Tue, 5 Dec 2017 02:32:23 -0700 (MST) DKIM-Filter: OpenDKIM Filter v2.11.0 mrfbl02-den.returnpath.net 396CB4A0966 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=senderscore.net; s=081107; t=1512466343; i=@senderscore.net; bh=a0NeazqrTZzEv6QjCrfFjbEmD8KzAp5JFlRJSvJt7d0=; h=Date:Subject:To:From:From; b=xiKSoBNXNMBGj8VSf0t9iXQnBdJN+Fb14O1GKuuK9BCgUD7SNMWo7irbDMkq/Sci0 2HhE/p2EEMhEwD05CJ5yN6uFmTzCgqU1qYpoS+jlK0m9Go6rgPc6+p23fI8LWzJohV JfuFiJ2YYvn1kJ4vrXr3TWGeAidG7gjepzZ0EUhQ= Received: by poma01.lan.returnpath.net (Postfix, from userid 106706) id 3655560493; Tue, 5 Dec 2017 02:32:23 -0700 (MST) Content-Type: multipart/report; boundary="_----------=_15124663432990616497"; report-type="feedback-report" MIME-Version: 1.0 X-Mailer: MIME::Lite 3.029 (F2.84; T2.04; A2.12; B3.13; Q3.13) Date: Tue, 5 Dec 2017 02:32:23 -0700 Subject: Yandex Abuse Report To: abuse@he.net From: feedbackloop@yandexfbl.senderscore.net Message-Id: <20171205093223.3655560493@poma01.lan.returnpath.net> Content-Transfer-Encoding: 7bit This is a multi-part message in MIME format. ----------=_15124663432990616497 Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain This is a Yandex email abuse report for an email message received from IP 65.19.141.67 on Sun, 3 Dec 2017 16:06:48 +0000 ----------=_15124663432990616497 Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: message/feedback-report User-Agent: ReturnPathFBL/1.0 Abuse-Type: complaint Arrival-Date: Sun, 3 Dec 2017 16:06:48 +0000 Feedback-Type: abuse Version: 1 Source-IP: 65.19.141.67 Original-Rcpt-To: ca2b45ef141c63af66829a2f346c832b@email.xxx Original-Mail-From: newrepub@johnny.heliohost.org Reported-Domain: email.xxx ----------=_15124663432990616497 Content-Disposition: inline Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Received: from <ca2b45ef141c63af66829a2f346c832b> by <removed> with LMTP id tMPEXTSj for <<removed@email.xxx>>; Sun, 3 Dec 2017 19:06:49 +0300 Received: from johnny.heliohost.org (johnny.heliohost.org [65.19.141.67]) by <ca2b45ef141c63af66829a2f346c832b> (nwsmtp/Yandex) with ESMTPS id pO6cfydXbH-6mLK4inb; Sun, 03 Dec 2017 19:06:48 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Return-Path: newrepub@johnny.heliohost.org Received: from newrepub by johnny.heliohost.org with local (Exim 4.88) (envelope-from <newrepub@johnny.heliohost.org>) id 1eLWmx-0003A2-Bm for <ca2b45ef141c63af66829a2f346c832b@email.xxx>; Sun, 03 Dec 2017 08:06:43 -0800 Subject: Welcome to New Republic Date: Sun, 3 Dec 2017 16:06:43 +0000 From: Gawmonster <admin@new-republic.org> Reply-To: Gawmonster <admin@new-republic.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" To: ca2b45ef141c63af66829a2f346c832b@email.xxx Content-Transfer-Encoding: quoted-printable <body removed> ----------=_15124663432990616497--
  6. If it's offering commercial films for free, then it's copyright infringement and will get you suspended. I can't check your sites since they're addon domains that are still queued right now. We don't allow piracy/illegal streaming sites
  7. Please clear your cache. Once that’s done, you’ll need to troubleshoot the 500 error your site is producing. The top reasons for 500 errors are incorrect file permissions (PHP files must be 644 to work, the default upload is 664, so they won’t run until you change them) or invalid htaccess files (rename it so it’s ignored and try again).
  8. Yeah, we mass-ban phishing/fraud/fake loot generators/etc. several times a day because we get so many. Yours got swept up my latest round this afternoon. And as Krydos said above, our criminals are dumb. Theres nothing like phishingstore.heliohost.org for hosting your phishing site. Would you mind posting a screenshot or other example of your content as well if you can? Edit: Beaten to it, so comments on Krydos response added.
  9. Can you explain what you’re planning to do with the domain you picked? Please note that phishing, fraud, and similar are not welcome here.
  10. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache. If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic you might consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator
  11. Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache. If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic you might consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator
  12. This support request is being escalated to our root admin.
  13. This may be an Apache restart. Whenever anybody on the server modifies a domain, all the sites experience a 15-60 second period where they won't load/take forever to load. My site uses a fraction of the resources of WP and still sees these delays on occasion. Usually the duration is short enough that it just goes through anyway, but on rare occasion it times out first. This is probably the cause of the 522 errors, since the server will not respond to requests during this time. Load spikes like that are usually users causing load or occasionally a DDoS hitting the server. These generally auto-remediate within minutes (it suspends the user or blocks the IP). A user did get suspended for high load on Tommy on the 4th, so a user overloading the server looks likely. This CloudFlare IP was blocked due to failed cPanel logins in Germany. Unblocked. I'll also escalate this to see if Krydos has additional comments and/or can whitelist the CF IPs.
  14. It was blocked for too many failed FTP logins. Check that the username and password are correct in your FTP client. Unblocked.
  15. The limit on Tommy is 4 concurrent connections per user. The entire server allows 150 connections at a time.
  16. You're suspended for severe high server load. I'll escalate this so we can identify the cause. I don't want to unsuspend this until you know how to fix it so we can avoid causing more downtime for users on your server.
  17. Try deleting it now. http://www.heliohost.org/classic/support/scripts/delete
  18. In that case, why do you have 2 accounts (you're only allowed one)?
  19. We saw what was probably a DDoS that didn't last. Everything went down at once and was down for about 2 minutes. Tommy also appears to have had 2 load spikes, whether that was a symptom of a DDoS or an abusive user, I don't know...http://heliohost.grd.net.pl/monitor/ Bailey's issue was one of the Tommy spikes. I saw it too, and I got several notifications about stuff that reaches out to my account not working (both were right around the top of the hour...). For HelioHost itself, HelioMine won't start mining if Tommy's down since the backend lives on my account (miners already running will keep going, but they can't start again if stopped). As for mysql going offline. if you're on Johnny, I've been seeing a lot of posts about that recently. It tends to recover itself in a few minutes, but it does seem to go down quite a bit more than it used to.
×
×
  • Create New...