wolstech

What do they look like in phpmyadmin? Do all the tables say "in use"? If so, it's because we dropped innodb support on Stevie and your choices are to wait and hope we restore that support, or drop them. As for backups, we don't keep any backups.

That account is not suspended. Timeouts are usually caused by you being blocked by our firewall. Moving to customer service.

I don't know why it was (or even if it was, the system said it was active, the account's behavior is what lead me to that conclusion). Something probably didn't work right when the system tried suspending you or unsuspending you for something else (inactivity most likely). cPanel and FTP never show any special message for suspended accounts, they just act like the password is wrong. Password resets (both how you do it, and how I do it) also won't work when you're suspended, which would explain why your attempts to reset it failed, and the password I sent you didn't work when tried (I only tested it myself after suspending and unsuspending you).

Rapidleech and proxies are probably the number one way to get suspended for load on Stevie, so they're almost definitely the cause of your suspension. Unfortunately, the only real solution is to just not use them. There's tons of free proxies out there you can use without running one here. You could also move to Johnny, which lets you use more resources, but has poor uptime so you'll find yourself unable to use your account quite a bit on Johnny.

Looks like the NS started working again after I removed its domain from that Johnny account. We really do need a blacklist though. This is the third or fourth time since I've been here that someone registered a system subdomain.

Try it again now. You were half-suspended I think...I suspended then unsuspended you, and the password I sent earlier is now working. It's working for me: https://www.dropbox.com/s/yrxmm5wtpwausoo/Screenshot%202015-10-09%2023.35.10.png?dl=0

We just updated it a month ago on Stevie, and a few months before that on Johnny. I don't think it'll be updated again for a while... Besides, there's more pressing things, like Stevie's MySQL, which doesn't work right (and is outdated). Johnny probably wouldn't cope well with extra stuff seeing it's already severely overloaded and down half the time.

I'm always surprised too. I've definitely seen people register stevie.heliohost.org and johnny.heliohost.org before as well... It's actually a valid (albeit empty) account on Johnny when visited. The result is sporadic though. Sometimes queued, sometimes an Index of /. I removed the domain from the account by changing it to ns1.heliohost.invalid, so we'll see if it fixes itself or if Krydos will need to fix this manually.

Your account has been manually unsuspended.

You need to fix the user not the database itself. The relevant tools are at the bottom of this page: http://stevie.heliohost.org:2082/frontend/x3/sql/index.html You should not need to touch any database tables, or even open PHPMyAdmin to fix this.

A new password has been emailed to the address on file for the account smartdog.

This support request is being escalated to our root admin.

Ns1 is supposed to be on Stevie IIRC. 64.62.211.131 is Johnny's shared IP...I'm not surprised it won't resolve dns, there's no nameserver there. The johnny account kuroneko has registered the ns1.heliohost.org as its main domain, which is why this happened. Escalating.

Here you go.

You can't reset your password when your account is inactive. You need to renew it first using this script: http://www.heliohost.org/home/support/scripts/renew

It's time since midnight. 21 would be 2100 hours PDT. 9 21 * * * would run your job at 9:09PM PDT every day...since you're in Germany, that's 6:09AM local time for you. I have a cron on my account that runs at 4:18PM EDT daily. It looks like this in cPanel (Item order: Minute, Hour, Day, Month, Weekday, Command): 18 13 * * * php -q /home1/rax/public_html/si3/webcron/cron.php

Not the database itself, the user for the database. You shouldn't need to use PHPMyAdmin at all. You should be able to everything needed to fix your using the tools at the bottom of this page: http://stevie.heliohost.org:2082/frontend/x3/sql/index.html

Try changing your database user's password to match what's in the config file for your website. If it doesn't work, delete and recreate the user for your database. When recreating it, make sure the password matches and that the new user is assigned to the database.

We're only -7 in the summer since we observe DST. We're GMT -8 in the off season. That cron would be wget dk.heliohost.org > /dev/null 2>&1 PHP is the command, since you're using wget instead, you don't need PHP. I'll be honest that your command is useless though. All that does is make your site download a copy of itself. Try changing your password for the PHPMyAdmin issue, if it doesn't help, it's caused by high load.

Check that your database contains expected tables in phpmyadmin. If the tables say "in use", you won't be able to use them and will need to either wait until innodb is fixed, or drop them and reinstall Wordpress (which will delete your content).

Is this still an issue?

The domain in question is now attached to a Stevie account with your email address hosting an empty WordPress install. Solved.

This seems to be working now for me. Please clear your cache and try it again if you're still having trouble. I've also noticed that since the update, old IE and Firefox don't work with the new PHPMyAdmin...

You need to change the database user password. You do that here at the bottom: http://stevie.helioh.../sql/index.html After changing it, verify the new password matches what's in your website's config file (wp-config.php in your case).

Your account is not suspended. The database issues are because mysql broke. You need to change the password for your database users and update the configuration file for your software to match the new password you set.