Krydos

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

How you gather your users info probably doesn't have a lot to do with this hack. How you *store* that contact information is more important. If you store it all as contacts online in your email account then if someone hacks that account they have access to all that information. If you store it all in a database then the hacker would have to gain access to that database to send spam to your customers. Let us know if you'd like some ideas on more secure ways to store your customers information.

We get the abuse reports when someone reports it as spam, but the number that matters is the date that the spam was sent. In this case all of the emails (so far) were sent on the 14th. Sometimes these spam reports continue trickling in for up to a month after the spam was actually sent. These particular emails look like they were sent via remote email client: X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] If it was sent via a hacked script it will usually have something that looks like X-PHP-Script: hackedwebsite.heliohost.org/wp-content/spamscript.php for 123.234.123.234 Anyways, the account waltersj has been unsuspended. Thank you for taking care of it so quickly.

The database hoba_ans 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 ablaty_tours 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.

What is the name of the database?

@ablaty Your topic has been split to http://www.helionet.org/index/topic/22780-database-dead-ablaty/

Dedicated IP granted.

The database likemike_tbd1 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 account afleet is still queued. You can check the status of your account creation by typing your username into http://www.heliohost.org/home/support/scripts/status Once your account is active the dedicated IP can be assigned to it. Also for future reference your username is afleet not afrikafleet.

The renew script is just as broken as it's ever been. Since Johnny was rebooted it is translating into a lot more load on Cody too. If Cody has too high of load for too long it breaks httpd, and apache has to restart. The higher the load on Cody the longer it takes to reactivate an inactive account. The longer it takes to reactivate the higher the chance of Cody httpd restarting during the reactivation which leads to the searching message never updating into an error or a success message since the request times out. The only thing that has changed was I added a single line of javascript to prevent people from submitting the form over and over. That's the only thing I can think of. I'll leave this thread open for a while in case someone has some information to add to this discussion.

Are there certain accounts that it always fails on? Certain browsers that it always fails with? I have yet to be able to reproduce the problem.

Only on Stevie, or are Johnny accounts doing the same thing?

The database sandy880_mainDB 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.

Thanks! As a free service we don't have an advertising budget because we would rather invest all of the money that we do have into providing better service and improving the servers so we really appreciate the word of mouth recommendations that our satisfied users provide. Feel free to post about us on social media like twitter, facebook, hosting review sites, your personal websites or blogs, and anything else you can think of. As long as we have clients using our service Heliohost will continue to exist.

The database snorriv_wp01 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.

Softaculous support has responded, and now Softaculous is back up and running on all servers. Thanks for alerting us to the problem. Let us know if there's anything else you need help with.

Why not just use https://developers.google.com/speed/pagespeed/insights/ on your site?

The database kristel_database 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.

What do you use your account for other than copyright infringement and pornography (both of which are against our terms of service)?

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 database twbrasil_flux333 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 jptiger_jrpwp 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.