wolstech

Delete the user euler_phpb519 in cPanel, then recreate it. Be sure to use the password found in phpbb's configuration file, and reassign the user to your database after recreating it.

Change your cPanel password then log out and in again: http://stevie.heliohost.org:2082/frontend/x3/passwd/index.html

I see Python 2.4, 2.7, and 3.4 on Johnny... If you want 3.4, try using this for the shebang line: #!/usr/local/bin/python3.4

Johnny accounts can take up to a week to start working due to load. You registered yesterday, so give it a few days

Huh. Seems to be broken on Johnny accounts...mine has the same problem. I'll escalate this for you.

The entire support staff here is volunteer, and only 1 person has the ability to do dedicated IPs. As a result...not really. If you want, you can begin installing software and creating content now. The SSL installation won't break your site except for a short (up to 24 hour) period of downtime where your site shows Queued while the changes take effect, so anything you do now will easily carry over once SSL is set up. Also, I highly recommend not using WordPress since it has a reputation of getting hacked. I permanently suspended 3 people this morning after their WordPress install was hacked and Phishing decided to set up shop. Just about every other CMS is more secure...

Whenever Krydos gets around to assigning the IP address for you. Usually a day or so at most. Once it's assigned, you'll just have to install a certificate to activate SSL.

This support request is being escalated to our root admin.

That error really should be more descriptive...it means you already have an account (in your case, on Stevie). Users are limited to one account. To sign up on Johnny, delete your Stevie account first, or request permission for two accounts in Customer Service (you need a good reason to have both).

Please see my response here: http://www.helionet.org/index/topic/23317-signup-problems/page__pid__114841#entry114841

He is online, but his uptime is terrible due to load. If you need something reliable, you need to use Stevie until the new server becomes available. Otherwise, just register on Johnny anytime.

@Byron: His username is war on Stevie.

Use this to renew it: www.heliohost.org/home/support/scripts/renew

That's a lot of emails considering the limit is 50 per day. I'll escalate it for you since I'm not sure what kind of email was being sent. Krydos might have more information.

Please clear your cache.

Be sure it's added in cPanel as a subdomain. Also, CloudFlare might be an issue...try adding an A record to your CloudFlare DNS. Name it loja.vnsmes.com and set its value to your shared IP (probably 216.218.192.170). Give it a few hours to update, then try accessing it again.

You'll get an email when you first register. The only time you'll get additional emails for a registration is if it fails. The second email would have the error message in it. If you're still waiting for cPanel to start working, check this script: http://www.heliohost.org/home/support/scripts/status Once your cpanel is active, that script will show an error, which is normal. If its giving an error, try logging in. You can also post over in customer service and we can check on it for you. Your domains will show Queued once the setup for the DNS begins. On Stevie, the queued page lasts 24-48 hours. On Johnny, up to a week.

Stevie is already back up. Seeing it was listed as preventative maintenance, it's probably things like disk scans, removing old temp files and logs, compacting databases, etc. Krydos would know for sure...

To add to Byron, crons run using services like easycron or setcronjob do not count towards your 2 per 24 hours (though I suppose running them too frequently could get you suspended for load...). Services like that are the recommended solution for people needing more cron.

The domain on your account was set to something invalid (didn't even look like it could be a domain...there was no TLD). Your domain has been manually changed to trevord.heliohost.org Please give it 48 hours to change, and up to a week to start working. I've also bumped your last login time to today since you were about to become inactive in 2 days.

The service you were providing (free access to TV and Movie content that would normally be paid for) is piracy, which is illegal in nearly all countries. Any hosting company you pick will suspend you for hosting these sites. The contents of accounts suspended for illegal activity cannot be recovered.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.

Once we have it installed. Last I heard, we still haven't gotten the plan upgrade we're supposed to get from our provider. That's been the big thing holding us back. Once we do, we have to physically have to install the server and put the software on it, then it can come online.

Your website's software likely has a security hole in it. Whatever software you're using, delete it and everything associated with it, and use a different program. Stay away from WordPress especially. It's notoriously easy to hack and is also very easy for the user to accidentally install malware as part of an extension or theme. When I first started here, I had a WordPress site like everyone else. After being hacked 4 times in 6 weeks, I deleted WordPress and wrote my own CMS. No hacks since...that was 4 years ago. Joomla has been known to have similar issues with extensions. The core product is fine in my experience. If you use it, make your own theme and don't use extensions from dubious sites. Nearly all CMS programs have this issue if you use "free" themes and extensions from random websites. Many of them are "free" in the sense that they're paid for by the malware contained in them. After an unknowing user installs the theme, the malware hiding in it is used to hack your website, then send spam, set up phishing, etc. to actually make money.

It's not that we can't set a hard limit on users for resources (we have that capability already), it's that we choose not to do so. We prefer to suspend individual users that cause a problem as opposed to punishing everyone by putting caps on them. If the server is busy, it's easier to get suspended than when its not. Not setting a hard limit means people can use it when the resources are otherwise wasted, but still deal with those who try to take more than their fair share. A hard line is the opposite of what we have and want. Also, seeing that we don't make much money, one of our goals is to spend it as wisely as possible. We'd rather not pay for something like this when we can serve our users without it. A hardware upgrade is a wiser investment (and one we just made ).