Jump to content

wolstech

Chief Risk Officer
  • Posts

    17,050
  • Joined

  • Last visited

  • Days Won

    617

Everything posted by wolstech

  1. You have to delete your account and sign up at midnight. The other way to move is to donate, in which case we can move your account directly instead of sending an invite.
  2. That's a known issue on Johnny. It's scheduled to be fixed the next time we rebuild Apache/PHP on Johnny. In the meantime, you'll need to either move to Tommy or wait until that extension is restored on Johnny though if you want to run that software.
  3. It was blocked for too many failed cPanel logins. Unblocked. It may take a few minutes to start working.
  4. Yep, everything in here is obsolete since the servers have all been rebuilt since then.
  5. It was blocked for too many failed web page logins. Do you have a restricted folder that requires a password (entering the password for such a folder incorrectly too many times is typically what gets you this block)? Unblocked.
  6. Please clear your cache to get rid of the suspended page. The cpanel performance is often slow on Johnny. It's normal for that server.
  7. You can pipe the email into a script so that the script receives the email and can act upon its contents. Take a look at the "advanced options" under the email forwarder settings in cpanel.
  8. Unsuspended. You have 24 hours from this post to remove the malware from your account. If we receive abuse reports or if the malware is still present in 24 hours, your account will be resuspended.
  9. This support request is being escalated to our root admin.
  10. Unblocked. It may take a few minutes to start working again.
  11. All of our servers are in the USA, though one can use our service from anywhere in the world. I think putenv will work, but not positive on that. It's not on the disabled functions list.
  12. You're suspended because your WordPress theme contained malware. WordPress is infamous for this, and we highly recommend that users do not use WordPress for precisely this reason (there's far too many fake/malicious themes and plugins for it out there anymore, and the core WordPress software is also known for vulnerabilities). You should delete your WordPress installation (or at the very least delete the "twentysixteen" theme and all of its files, including the one listed above) to remove the infection. I recommend finding different software entirely, but if you want to reinstall WordPress, be sure to use only up to date plugins and themes from reputable websites like the official WordPress site. I see several others in our system with that same theme that are also suspended...the theme appears to contain a backdoor. When you're ready to fix this, let me know and I'll unsuspend you.
  13. Using mysqli_fetch_assoc() instead is probably easiest. You get the whole row as an array instead of one field. The array indexes are the field names, so just look at the voto index of the array. Field names are case sensitive! The function returns null instead of an array if there are no rows left to get (or if the query returned no matching rows), so if using the output somewhere that an unexpected null will cause an error, you should check that the value returned is_array(). Details at: http://php.net/manual/en/mysqli-result.fetch-assoc.php In the below, assume $result contains the results of a mysqli_query() call, and that $result is not false (returned when the query fails). $aData = mysqli_fetch_assoc($result); //$aData['voto'] contains the value of the voto column for the first row in the result If your result returns multiple rows, you can call this in a while loop to get each row in turn and do something with it. The below would show the value of the 'voto' field for every row returned by the query: while ($aData = mysqli_fetch_assoc($result)) { echo $aData['voto']; }
  14. The server Stevie died 7 months ago (disk failure) and there is no backup available for that account (a backup is listed in our system but was unsuccessful). Unfortunately, you will need to start over.
  15. This support request is being escalated to our root admin.
  16. That's a lot of load. Did you install new software or receive a lot of attention (e.g. a reddit mention) recently? If you need help identifying the source of load (or get suspended for it again), please let me know and I'll escalate this so we can find out what file is causing it. Unsuspended.
  17. That error means something else sent output to the client before the session_start(). When output is sent for the first time (e.g. any HTML, an error message, an echo, etc.), the headers are sent along with it. You can't set a session cookie in an HTTP header that's already been sent, so the session_start() fails with that error. Odds are you either: have whitespace or HTML before the session_start() command, have PHP code that produces output (like echo) before the session_start() command, or have PHP that is generating an error (the error message that prints on the screen is output) before the session_start().
  18. It's for FTP, not email. Usually caused by entering/saving the wrong password in an FTP client. Unblocked. It may take a few minutes to start working again.
  19. If I remember right, Flask is installed for 3.6. Escalating to see if it can be installed for 2.7.
  20. This support request is being escalated to our root admin.
  21. If you deploy the second one, the first gets undeployed. War files are limited to one per account, and one per person (since you're only allowed to have one account). Escalating to have Zaxxon.war deployed.
  22. You can only deploy one WAR file. Which one do you want deployed?
  23. I wonder if the recent Johnny issues are the reason for this... Escalating.
  24. This support request is being escalated to our root admin.
  25. Unblocked. It may take a few minutes to start working again.
×
×
  • Create New...