Krydos

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.

Why not just provide a non-null value, the right data type, or a value within the specified range for all of the fields that give an error? For instance to fix the merchant_id error you could give it a default value, or you could give it a non-null value in the insert command.

Dedicated IP granted.

Please clear your cache.

Please clear your cache.

I don't understand why you would want a backup when all of your data is there: Oct 11 20:05 dtc_blog_wp/ Oct 1 2014 dtc_boxbilling/ Oct 7 08:30 dtc_esimmercadobd/ Mar 20 2014 dtc_sistemaunificado/ mysql> show tables; +-----------------------+ | Tables_in_dtc_blog_wp | +-----------------------+ | wp_commentmeta | | wp_comments | | wp_links | | wp_options | | wp_postmeta | | wp_posts | | wp_term_relationships | | wp_term_taxonomy | | wp_terms | | wp_usermeta | | wp_users | | wp_wpmm_subscribers | +-----------------------+ 12 rows in set (0.00 sec)

Yes, Mysql on Stevie will be updated eventually. We upgrade Johnny first to make sure the new versions are stable, and make sure there aren't any conflicts with our systems before updating Stevie. This is part of the reason Stevie has so much better uptime, and is so much more stable than Johnny. If you want the newest possible version of software as soon as possible though Johnny is the server to be on. Thank you for your input on what we should upgrade next. We value your feedback.

Here's your problem: /home1/ignasi/public_html/wp-content/plugins/hello.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/advanced-custom-fields/core/controllers/alias.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/advanced-custom-fields/core/fields/_base.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/advanced-custom-fields/core/fields/checkbox.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/jquery-updater/user.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/polylang/js/inc.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/codestyling-localization/images/template.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/codestyling-localization/languages/global.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/easy-contact-forms/forms/proc/_frm20.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/easy-contact-forms/forms/proc/_prc11.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/easy-contact-forms/forms/styles/ajax.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/easy-contact-forms/js/tinymce/plugins/table/session.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/easy-contact-forms/styles/std/files.php: Php.Malware.Mailbot-1 FOUND /home1/ignasi/public_html/wp-content/plugins/seo-ultimate/modules/modules/article.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/seo-ultimate/modules/index.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/seo-ultimate/plugin/class.su-installer.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/wordpress-seo/tests/header.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/wordpress-seo/languages/xml.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/plugins/wordpress-seo/uninstall.php: Php.Trojan.StopPost FOUND /home1/ignasi/public_html/wp-content/plugins/wordpress-seo/db.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/themes/wagon/option-tree/index.php: PHP.Trojan.Uploader FOUND /home1/ignasi/public_html/wp-content/themes/wagon/page.php: Php.Trojan.StopPost FOUND It looks like pretty much every plugin and theme that you installed on your wordpress was malware.

The fix hasn't been fully implemented yet, so no databases are invisible to anyone on Stevie. Like wolstech said if phpmyadmin isn't working for you please visit http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html and change your password. This syncs the cpanel and mysql passwords so cpanel can log in to phpmyadmin. If your websites aren't able to connect to their database then visit http://stevie.heliohost.org:2082/frontend/x3/sql/index.html and delete the mysql user that isn't working, recreate it, and assign it permissions, and the same password that it was using before. You can even change passwords if you wish but you'll have to update your scripts to use the new password. Let us know if you need more detailed instructions on how to achieve what I have explained.

It looks like it was partially removed so I removed some remnants that were leftover. Johnny is currently running Mysql 5.6.21. The instructions for switching servers is located at http://wiki.helionet.org/Moving_your_account Stevie is currently running PHP 5.3.8, and Johnny is running PHP 5.4.41. You can choose whichever you need and switch servers if you wish by using the above link. What did google support say about this error? I've seen people send unsolicited email through the google servers, and get this sort of error so it might be a problem with your specific account. None of the IPs that Heliohost own are currently listed for spam, and I can send and receive emails through my google account just fine. What did mandrill support say about this error?

Go ahead and create a new account now. Let us know if you have any error messages and we'll take care of them.

I'd like to clarify slightly that with the assistance of an admin you can retain use of your .com domain hosted with us, but you will not be able to create a new account with that main domain without assistance. Sorry for the inconvenience.

I just resuspended his account with the ACP, and then unsuspended and it worked just fine. Maybe it was just a temporary issue?

Thanks for the update. To some people it may seem like a waste of time to post again after the issue is resolved, but thousands upon thousands of people browse this site to find solutions to their own similar issues. When you post a final update like that it may end up helping all sorts of people down the road. If they find this thread it may even mean they don't have to post their own support request and that makes the administrators jobs even easier. Thanks!

Your account has been set to the x3 theme.