wolstech

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

Just help out where you can (customer service and questions are the best places to start). The people we promote are the people we see helping out on the forums. There's 2 ranks above yours that people can get promoted to, Moderator and Support Admin. There's also Root Admin above the Support Admin, but I don't know if someone can get promoted into that since until 3 weeks ago it was reserved for the founder... As for Java Requests...I can't even do those. The 2 root admins are the only ones that can.

It'll likely work. That error means your nameservers are not ours. You can't add domains if their nameservers are not set to ours.

You can't. Don't worry about it, we'll delete it when we see it.

Second time for malware. Escalating so the files can be removed.

49 hours for delivery, ouch. I'm not sure what else it could be beyond Johnny just being too busy to accept it. I'm assuming this happens regardless of what email service the sender used to send the email to you... I'll escalate it. Krydos might be able to figure out if its on our end.

Can you fix that formatting? The board seems to have mangled it.

Watermarks are about as good as you'll get. Even if you can't stop copying, you can at least get some credit where due. Hotlink protection is only useful for the lazy and for cases where hosts have bandwidth restrictions (which we don't have). Nothing stopping someone from downloading and sticking it on imgur there.

Nope. Sniffing traffic for usernames and passwords is impractical as the effort needed to spy on a specific network or user to sniff the traffic needed to log into a user's account would exceed the effort needed to just gain access by hacking the user's website. Hacked accounts here at Heliohost are usually a result of a user not installing updates or the user unknowingly installing malware on their account, hidden in extensions and themes for various CMSes... Another major reason for our decision is because AdSense pays significantly less on secure sites. The ads on our website, forum, and cPanel are our only source of revenue. Also, if you're not aware, Stevie and Johnny actually do support HTTPS for cPanel (try https://stevie.heliohost.org:2083, warning is because it's self-signed) for those who are concerned, however your logon won't be counted for inactivity because browsers block insecure elements from loading on secured pages.

I'm assuming the content is something like pictures posted on a public website. Visiting a site would make a visitor's browser download it to show it. At that point, they could just save the content file, so nothing you do on the server will matter. If you don't care about the general public not being able to view it, put the content behind a password wall or something so they can't access it without approval. The best advice though: If you don't want it copied, don't publicly post it on the internet.

Are you on Johnny? If so, they won't deliver when the server is down (which is a lot on Johnny), and it's on the sending person's mail service to try again (often it's 12 hours between attempts, and after 3 to 7 days returns it to the sender as undeliverable, so with a ~50% chance of Johnny being up, it could easily take a day or more if there's 2 or more failures before succeeding). Also, are the people sending mail to you using hotmail, GMX, or comcast? They have known issues with our service, though usually the issue with them is people not receiving your email, not the other way around.

Your account was suspended for running too many cron jobs. To help keep load low, we limit accounts to two (2) cron executions in a 24 hour period. This means that, if you only have a single job, it can run no more frequently than once every 12 hours, with two jobs, they can each only run once a day, and so on. Your account has been unsuspended.

The expired certificate was for testing purposes only. Heliohost.org and Helionet.org do not support SSL connections. Please connect using regular HTTP. Please clear your cache if it tries to redirect to a secure connection. We've made the decision to not support HTTPS on our website and forum for the time being.

He oddly asked to keep the other one in a second topic since it had his domain. The account arzip11 was unsuspended and arzip1 has been kept suspended. www.helionet.org/index/topic/23249-suspended-hh-arzip1/page__pid__114651#entry114651