wolstech

Change your password through cPanel here: http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html After that, log out then back in and try PhpMyAdmin again. For database users you created in cPanel, you may need to delete and recreate them before they work.

Did you recently renew it for inactivity? I've been noticing that ever since the upgrade on Stevie, accounts can take a while to fully unsuspend. It shows as suspended for me as well. If it's still not working by tomorrow night, I'll escalate this for you.

cPanel's restore tool can do that sometimes. I'm assuming you have a .sql file. Try this: Create an empty database in cPanel. After creation, open PHPMyAdmin, and navigate to that new database. Use the Import tab to restore the backup into the new database (might take some time after you select the file). Verify the contents of the database are correct.

You cannot move just one email address except for forwarding as Ice IT suggested. To properly use the new service, you probably need to change your MX records to whatever Google wants. They should provide directions what you need your MX records to be set to, and there may be some TXT records as well. The exact values will need to come from Google. As for the 50/day limit we have, Krydos might increase that if you ask (and agree not to send bulk mail). I know people have asked before and gotten it raised. If you want, I can escalate this and see if that's possible instead.

You don't mention a specific error, but I'll assume it's InnoDB related since most issues for backups failing to restore are. Make a copy of the backup, then open the copy in a text editor and do a find and replace in your backup, replace all ENGINE=InnoDB with ENGINE=MyISAM After that, save, and try to restore the edited version. Stevie currently does not support the InnoDB engine.

Most that needed to use their sites converted to MyISAM in the 18 months it was broken. You should do the same. I don't know when or if InnoDB will be restored.

You might be blocked, especially if you use FTP heavily. Also, you mention cron...just be aware that you can't run more than 2 crons a day. If you set a cron for every hour, you'll get suspended by the system. Moving to customer service.

It didn't fix the problem. It's part of a fix that I don't think is fully implemented yet. On the upside, with it entirely disabled, MySQL shouldn't crash so much because you can't even do stuff like try to create innodb tables. It just errors saying unknown engine instead of crashing the server.

Delete the database user and recreate it. A lot of database users got lost in the recent update it seems.

For software running on Johnny, use localhost to access MySQL. For remote connections, enable the remote access in cPanel, then use johnny.heliohost.org as the host.

The Access Denied errors seen on websites are fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it. PhpMyAdmin and your cPanel MySQL account are still broken though (sometimes changing your password will fix these, but it did not when I tried it).

The Access Denied is fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it.

These seem to be fixable by deleting and recreating the database user. Be sure to reassign it to the database after deleting and recreating it.

It was indeed dead database users. I deleted mine and recreated them and they work. Still doesn't explain PHPMyAdmin though...

Doesn't seem to be up. All my sites are still showing the access denied error and I can't even get into phpmyadmin. InnoDB was turned off a week or so ago, before this issue happened. InnoDB tables all show as "in use" now, and imports will fail with "unknown engine" as opposed to ghost tables.

Give it 24 hours then clear your cache. If it's still suspended after that, please let us know.

It appears to be a botched update, though at least one other user reported speaking to Krydos on IRC and who said he was unaware anything was updated (confused there, he's the only one who does this stuff). I've yet to hear anything official on this...nothing has been said to staff either. :-\

There's a lot of users on Stevie with this issue. I'm affected too There's been no information on this issue, even internally to the mods. I'm hoping it gets fixed soon. Moving to customer service.

You're on Stevie. Many if not all people on Stevie can't use their databases right now because MySQL is completely broken. Instead, you'll see a "can't connect" or "access denied" message. There is no fix but to wait until we hear from Krydos about this.

You're not alone. A large number of people on Stevie can't access their databases right now. The database server on Stevie appears to be broken.

Many people on Stevie are affected. The database server appears to be broken. It's up but returning access denied errors for the accounts.

Agreed. I suspect this is part of an effort to do to Stevie what we did to Johnny a few months back. Similar upgrades were performed, and we fixed the busted InnoDB support while at it. I just wish there had been notice...I published a software update on Saturday, and many sites are rejecting my software submissions because the forwarding links I use to track statistics return errors instead of 301 redirects right now.

cPanel definitely got upgraded. PHPMyAdmin was displaying a "This functionality is currently unavailable because a cPanel/WHM upgrade is in progress" message last night when I tried to log in. PhpPgAdmin was doing the same thing. cPanel went from 11.3x.x to 11.42.1, and I think MySQL went from 5.1.68 to 5.1.73 (though this may have happened earlier). If Krydos didn't know about it, then I'm confused. Nothing has been announced either publicly or to mods/admins, and only Krydos does major updates.

Nobodies does. Everyone on Stevie is affected. Not sure when it'll be fixed, but it was likely related to what looks to have been a cpanel update yesterday.

The database server is down entirely. Phpmyadmin is giving a message saying cpanel is being updated, which is odd.