Krydos

The database lucasl_wp954 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

Are you still getting that error?

Yeah, you should be good now.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database marko25_wp49 should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database raqbul_wordpress should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database alirss_w should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database forge254_mdb should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database tcode_myySubForum should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database brilli_ConfTool should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database susy79_league should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

That database doesn't exist, but I assume you mean (and I restored) fedeener_monitoraggio. The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases stefaanc_astrodb, stefaanc_logboeken, and stefaanc_tests should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

@kharasyn Your post has been split to http://www.helionet.org/index/topic/22289-mysql-invisible-kharasyn/ @predict The database predict_soccerway should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The databases listed should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected databases. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

The database domotica_jervis should now be visible to your root mysql account. You may need to delete, recreate, and reassign permissions to any database users that should have access to the affected database. If phpmyadmin doesn't log in properly or you don't see the database there change your account password and this should sync up the mysql/cpanel passwords. Let us know if you're still having any issues accessing your data.

Oh wow, you're right. I compared the source on your account to the logaholic website download, and they match. I've never seen legitimate php software use such suspicious looking code before: <?php eval(base64_decode("Ci8qIExvZ2Fob2xpYyBXZWIgQW5hbHl0aWNzIHNvZnR3YXJlICAgICAgICAgICAgIENvcHlyaWdodChjKSAyMDA1LTIwMTMgTG9nYWhvbGljIEIuVi4KICogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg... etc I just saw that your account was suspended for high load, checked your high load logs, saw that filename, checked the contents of the file, and assumed it was malware.

The file that triggered the suspension for Html.Exploit.CVE_2015_0072 has been removed. The file that got your account suspended for high load is /home1/lepsgnr/public_html/jogosdobotafogo.com/log/profiles.php which still exists and is clearly malware.

Woltech said it all already. The only thing I really have to add is that if you decide you don't want to go with the wildcard certificate due to it being rather expensive you could also purchase two single domain certificates. You will need to purchase 2 dedicated IPs from us for $24. The last person who inquired about getting a wildcard certificate decided this was the much more cost effective way for their particular situation. Let us know if you make the $12 paypal payment, and the dedicated IP can be assigned to your account.

Here is the email that got reported as spam: We have received a complaint about your account. Please investigate and fix within 24 hours. Hurricane Electric Abuse Department support@he.net From scomp@aol.net Fri Oct 2 04:48:54 2015 Return-Path: <scomp@aol.net> X-Original-To: report@abuse.he.net Delivered-To: report@abuse.he.net Received: from smr-a03e.mx.aol.com (smr-a03e.mx.aol.com [204.29.186.242]) by abuse.he.net (Postfix) with ESMTPS id 8AAEB5405C2 for <report@abuse.he.net>; Fri, 2 Oct 2015 04:48:51 -0700 (PDT) Received: from scmp-d010.mail.aol.com (scmp-d010.mail.aol.com [172.29.189.79]) by smr-a03e.mx.aol.com (AOL Mail Bouncer) with ESMTP id 55270380020B for <report@abuse.he.net>; Fri, 2 Oct 2015 07:48:50 -0400 (EDT) Received: from scomp@aol.net by scmp-d010.mail.aol.com; Fri, 02 Oct 2015 07:48:45 EDT To: report@abuse.he.net From: scomp@aol.net Date: Fri, 02 Oct 2015 07:48:45 EDT Subject: Email Feedback Report for IP 65.19.143.2 MIME-Version: 1.0 Content-Type: multipart/report; report-type=feedback-report; boundary="boundary-1138-29572-2659438-26296" X-AOL-INRLY: stevie.heliohost.org [65.19.143.2] scmp-d010 X-Loop: scomp --boundary-1138-29572-2659438-26296 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit This is an email abuse report for an email message with the message-id of received from IP address 65.19.143.2 on Fri, 2 Oct 2015 07:40:11 -0400 (EDT) For information, please review the top portion of the following page: http://postmaster.aol.com/Postmaster.FeedbackLoop.php For information about AOL E-mail guidelines, please see http://postmaster.aol.com/Postmaster.Guidelines.php If you would like to cancel or change the configuration for your FBL please use the tool located at: http://postmaster.aol.com/SupportRequest.FBL.php --boundary-1138-29572-2659438-26296 Content-Disposition: inline Content-Type: message/feedback-report Feedback-Type: abuse User-Agent: AOL SComp Version: 0.1 Received-Date: Fri, 2 Oct 2015 07:40:11 -0400 (EDT) Source-IP: 65.19.143.2 Reported-Domain: stevie.heliohost.org Redacted-Address: redacted Redacted-Address: redacted@ --boundary-1138-29572-2659438-26296 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <support@securitycenter.com> Received: from stevie.heliohost.org (stevie.heliohost.org [65.19.143.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mtaig-aab04.mx.aol.com (Internet Inbound) with ESMTPS id 4BF4C70000090 for <redacted>; Fri, 2 Oct 2015 07:40:11 -0400 (EDT) Received: from [45.32.253.188] (port=39880 helo=zeebroo.com) by stevie.heliohost.org with esmtpa (Exim 4.82) (envelope-from <support@securitycenter.com>) id 1ZhyhU-0002Dx-KC for redacted; Fri, 02 Oct 2015 04:40:06 -0700 From: Support <support@securitycenter.com> Subject: zeebroo.com,admin@zeebroo.com,12345 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - stevie.heliohost.org X-AntiAbuse: Original Domain - aol.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - securitycenter.com X-Get-Message-Sender-Via: stevie.heliohost.org: authenticated_id: admin@zeebroo.com X-Source: X-Source-Args: X-Source-Dir: x-aol-global-disposition: G Authentication-Results: mx.aol.com; spf=none (aol.com: the domain securitycenter.com appears to have no SPF Record.) smtp.mailfrom=securitycenter.com; x-aol-sid: 3039ac1a7ec6560e6d1b3954 X-AOL-IP: 65.19.143.2 X-AOL-SPF: domain : securitycenter.com SPF : none He man what are u doing? --boundary-1138-29572-2659438-26296-- If your account gets reported for spam again the suspension may be permanent. Please fix the problem swiftly. Your account has been unsuspended.

Here's the error I get: { "error_message" : "This IP, site or mobile application is not authorized to use this API key. Request received from IP address 65.19.143.2, with empty referer", "html_attributions" : [], "results" : [], "status" : "REQUEST_DENIED" } { "error_message" : "This IP, site or mobile application is not authorized to use this API key. Request received from IP address 65.19.143.2, with empty referer", "html_attributions" : [], "results" : [], "status" : "REQUEST_DENIED" } My guess is that you might have to add Stevie's IP to a safe list of some sort to use that API.