wolstech

Verify that your URL does not start with https. Also, try removing the cloudflare and using our server directly.

FileZilla should have an option to limit the number of connections it uses. Try setting that to 3. Try passive mode if not already using it. I've also seen it happen for no good reason. In that case, just ask to be unblocked again. Finally, Wordpress is very easily hacked and abused. Stay away from "free" themes and plugins off of random sites. Try to find these on sites like wordpress' own listings. Dubious themes are notorious for malware, spambots, and backdoors, and plugins can also be malicious. Keep everything up to date at all times.

Nothing was updated in Stevie. This problem does not exist on that server.

Looks like we either need php or MySQL fixed. The error comes from using a MySQL version different from what php's mysqli library is for. Seeing we fixed MySQL recently on Johnny, I bet we updated it and didn't update the php libraries. Escalating.

That's the firewall. Too many connections over FTP is the most common cause. I'll move this to customer service so an admin can unblock you.

Stevie was not down at all today per the monitor: http://heliohost.grd.net.pl/monitor/ If you cannot access anything, you might be blocked in the firewall. Can you log into cPanel?

MySQL 5.5 is available on Johnny and will eventually make its way to Stevie. There are no immediate plans to update php. When we finally do, it will be updated on johnny first. We support all software requiring php 5.3.x. Software requiring php 5.4, 5.5, or 5.6 may or may not work, and officially is not supported here.

We broke a bunch of databases trying to fix the frequent database server crashes. Krydos has to fix this. Escalating.

I see "UNOFFICIAL OTA Server by BioGenX". Please clear your cache.

You were suspended for spam. I'll escalate this.

Your forum account and hosting account are not connected to each other. You can receive hosting email without validation. In fact, we currently don't have email validation for hosting, though we hope to change that in the future to improve communication and reduce the number of spam and phishing accounts we get. Only forum accounts require email validation before you can post. You don't need to validate anything right now since you can already post.

You were suspended for running 4 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.

This support request is being escalated to our root admin.

I'm getting DNS errors for the heliohost.org subdomain, and newforte.cf is still queued. This should have been setup by now (8 days).

It can't be marked solved since it's in the web section. This really should be a customer service topic. I'll move it and mark it solved for you

Install it manually. For details, see http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ (this issue is listed near the bottom of the first post)

Their website does use it in many cases. It's read only so they can't change anything, but their websites at least show up when viewed. If it were missing entirely, they'd be getting an error about the database not existing.

Most of our users register with emails that they don't check or are invalid since we don't verify them (we hope to change this at some point to require email validation). Some use providers that won't receive mail from us. The large majority also never visit these boards, so warnings here are moot. The only solution I can think of is to put a nice big banner at the top of cpanel about it, since they have to login so they aren't suspended due to inactivity. We'd then need to leave that there for several months before we do anything so everyone sees it. Finally, we'd need to fix it and deal with complaints we'd get from those that ignored the warnings. Not really practical.

So back up damaged data, fix the (not broken) software, then restored damaged data? That'll leave us where we are now. The databases themselves, not the software, are the problem. We do not have backups of any form, and there is no way to create one that would be useful. The server is beyond repair unless we want to permanently delete every innodb database on the server. TL;DR: It can't be fixed without losing data, otherwise it'd be fixed already.

Not necessarily. It will open the databases, then try to write to them and crash doing so. The whole point is to let users keep using their databases in read-only. Removing that folder would delete the data.

Just use http://stevie.heliohost.org:2082 or the form on the bottom of heliohost.org. The way to tell if the login counted is to look at the URL after login. If it ends in .phpcp it should count. If it ends in .php and .html, it will not count. Your last login is showing as today, so it counted when you logged in today.

It's still working for me. I cannot get a single error from that site. That error message is also not from our servers. Our error messages do not mention CentOS at the bottom (they say Unix instead), and Apache is the wrong version as well. You need to remove those other NS records from your domain, as those are likely the cause of this issue (when someone hits your domain and it picks one of those NS's instead of ours, you get the error pages from another server instead of content from us). Try entering ours repeatedly in the other boxes. If it won't accept them, you may need to contact your registrar to have them removed.

Seeing that cP and your DB users have this problem immediately following being unsuspended, the issue sounds like your account's passwords were not unscrambled when you were unsuspended (server probably choked on load or something). The passwords for the DB users need to be changed. Go here: http://stevie.heliohost.org:2082/frontend/x3/sql/index.html Go down the bottom of the page and click the username of the affected user to change the password. After that, your software's config file needs to be edited with the new password (how and where that's done will vary by program, should be easy to find in the help for the software or on Google).

It's working for me, 3 hours after your post reporting it working. We'll see if it continues working, but I wonder if this might have been a cache issue or something...

Code 1045 is an access denied error, so cP has the same problem as your website. Go here: http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html Make sure "Allow MySQL password change" has a checkmark, then change your password. After that, log out then in again and see if phpmyadmin works. Your website could be a bunch of things. Did you create a mysql user and assign it to the database you're using? Is the password correct? You should not be using your cpanel account for database access in a PHP program (security issue).