Jump to content

wolstech

Chief Risk Officer
  • Posts

    16,404
  • Joined

  • Last visited

  • Days Won

    584

Everything posted by wolstech

  1. FTP is usually the cause, though the reason given is usually "FTP 200 connections" or the like. Sometimes, it just happens. If it recurs, we can look into it.
  2. That account's main domain is already set to jimbo1qaz.ro.lt and the site is working: http://jimbo1qaz.ro.lt/
  3. It appears you tried renewing it. The renewal script currently does not work for Stevie accounts. Your account has been manually unsuspended.
  4. You're welcome! I'm glad to see you got it working.
  5. This is your issue. The easiest fix is to select "All Privileges" at the top when asked; most people just do this to make it simple. If you want, you can manually select CREATE, ALTER, DROP, SELECT, UPDATE, INSERT, DELETE, which are the most commonly needed privileges.
  6. That message means "cPanel thinks this user exists, but when it asks MySQL to change its password, MySQL says it does not exist". Just delete the user and recreate it. Use the username and password you got in wp-config.php when you create the new one. Also, be sure to assign the new user to the database you use for Wordpress.
  7. The error about the old MySQL version is irrelevant and can be ignored (we aren't planning to upgrade as far as I know). Your issue is with your database user or your wp-config.php (the database user and its password need to be correct in that file). The user must also be assigned to your database. Restoring the database is unlikely to fix the problem. If you're sure you've checked all this, I'm not sure what else is wrong. Every other case we've seen has been caused by one of the issues mentioned.
  8. Your database users need to be deleted and recreated. You can do that here: http://stevie.heliohost.org:2082/frontend/x3/sql/index.html (Make sure the password for the new user matches what's in the configuration file for your software). Change your cPanel password to fix PhpMyAdmin. You can do that here: http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html
  9. 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.
  10. That account is not suspended. Timeouts are usually caused by you being blocked by our firewall. Moving to customer service.
  11. 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).
  12. 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.
  13. 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.
  14. 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
  15. 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.
  16. 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.
  17. 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.
  18. A new password has been emailed to the address on file for the account smartdog.
  19. This support request is being escalated to our root admin.
  20. 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.
  21. 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
  22. 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
  23. 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
×
×
  • Create New...