Jump to content

wolstech

Chief Risk Officer
 View Profile  See their activity

  • Posts

    17,978

  • Joined

  • Last visited

  • Days Won

    675

 Content Type 

Everything posted by wolstech

  1. wolstech
    You were erroneously suspended...suspended users cannot reset their password. You've been unsuspended. Try logging in/resetting again. Also, an empty form action is actually valid HTML. Empty actions send the POST to the URL you're currently on (basically, the page posts the data to itself, which causes it to reload and send the output back for viewing).
  2. wolstech
    Unsuspended.
  3. wolstech
    Delete the user and recreate it. Then try again.
  4. wolstech
    Your username will always be all lowercase: micasita Please check your email.
  5. wolstech
    Accounts take 24-48 hours to start working. Since you just registered today, this is normal.
  6. wolstech
    It can't be suspended because the server isn't even running. If we manage to fix Johnny, your account should just come back on its own. We don't do inactivity suspensions for a while after such events, so you should just be able to log on when it comes back up to catch the last login date up, and you're good. In the meantime, you're welcome to make a Stevie account, but there's no java support there (which you needed IIRC).
  7. wolstech
    This support request is being escalated to our root admin.
  8. wolstech
    You're welcome to create a Stevie account, but unless you want to rebuild your site, not really.
  9. wolstech
    The hardware failed, so not until at least late August when someone can travel to look at it in person. We don't even know if its repairable or not yet, though we think it might just need a new hard disk.
  10. wolstech
    It's not suspended, the hardware Johnny lives on kicked the bucket. If you wish, you are welcome to sign up on Stevie. If you do, use a different email, domain, and username, then let me know you signed up. I'll have Krydos or Byron remove your ivanwalls.com domain from your dead Johnny account so you can host it on Stevie.
  11. wolstech
    The users all got lost a few weeks ago, but cPanel isn't aware that MySQL no longer has a user by that name. Just delete the user in cPanel and recreate it. Then reassign it to the database.
  12. wolstech
    It's ok to leave the old one. There's nothing you can do about it anyway. A root admin would need to drop it for you. I'd just keep using the new one.
  13. wolstech
    That website is working normally for me...is there a specific page that doesn't work?
  14. wolstech
    No problem. Things happen sometimes. Let us know if you need anything else
  15. wolstech
    Looks like it got caught up in the account database restore...said active but was suspended... It's been unsuspended.
  16. wolstech
    What is your username?
  17. wolstech
    We don't keep backups. You need to use your own backups, or if they don't exist, try to fix your wp5555 database instead.
  18. wolstech
    What's your username and the names of the databases that need restored?
  19. wolstech
    It should. You can also use http://stevie.heliohost.org:2082/ to log in and it will count.
  20. wolstech
    Delete your database users, recreate them, and reassign them to the databases. Make sure to use the same password that's in your software's config file.
  21. wolstech
    You've been unsuspended.
  22. wolstech
    If it's already parked, they're functionally the same. Just park it in cPanel if it's not already, and use it the same way as you would your main domain (we recommend keeping the .heliohost.org domain anyway...Freenom has been known to randomly cancel domains). Also, with Charlie crashed, there is no way for most of us to change it. A root admin is the only one who can change it. Do you want me to escalate it for you?
  23. wolstech
    Glad to see you got it working
  24. wolstech
    Yeah, I missed the edit. Surprising to see indexes eat so much space, but if you can drop some of the indexes to make it fit, that works
  25. wolstech
    Overhead possibly, but that seems excessive. I'm not too sure what's up with this at this point. I didn't realize the 213MB was an uncompressed dump (I thought it was compressed, which would make 840 reasonable)...the dump as you said is nearly always larger than the DB produces. As for another place to host this, I'm not sure...I've always had mine run here or on a local PC.
×
×
  • Create New...