wolstech

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.

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']; }

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.

This support request is being escalated to our root admin.

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.

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().

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.

If I remember right, Flask is installed for 3.6. Escalating to see if it can be installed for 2.7.

This support request is being escalated to our root admin.

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.

You can only deploy one WAR file. Which one do you want deployed?

I wonder if the recent Johnny issues are the reason for this... Escalating.

This support request is being escalated to our root admin.

Unblocked. It may take a few minutes to start working again.

It's archived because you didn't log in and it was inactive for too long. Escalating so it can be restored.

That account is permanently suspended for phishing. Also, you appear to be posting from the same computer or network as https://www.helionet.org/index/topic/28874-solved-request-unsuspension/ (also phishing). If you're the same person, please be aware that you're only allowed one active account, and that phishing sites are not welcome on our service. Please create a new account.

Your IP is not blocked for FTP login failures. However, that account is permanently suspended for phishing. Please create a new account.

Because the cell phone is probably seen by us using its cell plan IP. Cell phones on a data plan can change IPs very frequently (every few minutes, or even seconds). Try seeing if you can put the device in airplane mode, then turn on the wifi while in airplane mode. Apple devices can do this, not sure about Android. This disables the cell network connection and forces the data to go over your wifi.

It did have a short burst of downtime around 10AM PDT: http://heliohost.grd.net.pl/monitor/ I got notifications on my phone for it, which means it was down for more than 2 minutes (my monitor reported 4m 56s). The server probably was busy with something like Apache restarting (which causes a short load and downtime spike like this).

Unblocked. It may take a few minutes to start working again.

You're actually blocked for failed IMAP logins. Did you change an email password recently and forget to update the password on a phone or mail client? Either way, you've been unblocked.

Un-escalated and marked solved.

If you connect with FTP, you'll see them. Otherwise you need to go into the File Manager's options in cPanel and select "show hidden (dot) files". I'll escalate it to see if Krydos can fix this for you. Worst case is you can always delete your account and sign up again.

Check the .htaccess in the public_html folder and rename/delete if present. Also verify public_html has 750 permissions. Rename your index.php. If that doesn't help, let me know and I'll escalate.

To add to Krydos, we also only allow one account per person unless you ask for permission for a second. If you request permission and are approved, the account generally needs to be on a different server.