wolstech

If you still see that at this point, please clear your cache.

This was answered as part of this one: https://www.helionet.org/index/topic/40461-hh389017-urgent-installing-ssl/

That account is already active. If you see a queued page, please clear your cache. As for inactivity, in fairness to others, we are unable to do this for free accounts. It's been offered to donors though, and I know it was also one of the fundraiser gifts last year.

The link you sent still works but is outdated because ZeroSSL works differently and has limits and a registration requirement now. Some others have recommended sites like sslforfree.com to get certificates instead. There's a discussion about ZeroSSL alternatives on our forums that may be of interest: https://www.helionet.org/index/topic/40155-alternatives-for-zerosslcom-getting-lets-encrypt-certificates/?view=getnewpost

@sohamb03: it sounds like you misunderstood (or perhaps I explained badly). The way this works is it suspends accounts *until* the load comes down. It doesn't suspend users who don't make any load, that'd be pointless. Also, an account that's suspended produces no load at all, it just wastes space. If you had a list of accounts and sort them by heaviest use at the top, the logic is (oversimplified): "suspend account at top of list, recheck load, repeat if still too high". I have seen cases where the chart doesn't show a lot of load, but the user gets suspended for it. These are "spike load" suspensions. My understanding is that the chart Krydos shows reflects an *average* of an account's use for the day, so an account that normally doesn't produce much load could spike from nothing to the top (from, say, a bad script executing) and suspend, and it won't look too bad on that chart. @Krydos: How often does that chart update? Is there a sampling rate for that data?

If your system opens a port (which it probably does if it needs a server half running), no it won't work on the shared hosting. You could buy a VPS to run it though. If it doesn't need to open a custom port and only has to be accessed by stuff running on the hosting server, it might work using a cron, but leaving things running infinitely like this is a good way to get suspended too because they contribute to load while they're running.

Space meter sometimes takes a few minutes to update. Also, check in your temp ~/tmp folder, the stats data loves to eat large amounts of space...

This guy promptly moved his phishing campaign to a host called Hoststud (a tiny cPanel startup running on what looks to be a Hetzner VPS) after we banned him...I just managed to get him shut down over there too.

You're running WordPress, which is infamous for this. Krydos has written extensively about why we recommend users stay away from WP, but high load and security issues are the top two reasons. To give you an idea, a WP site can generate more load serving a few MB of data, than most other CMSes would generate while serving several GB worth of data. The only real fix for it is to dump WP and find something else to build your site with.

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. If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic, you might want to consider purchasing a VPS instead. https://www.heliohost.org/vps/ VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access.

It looks like it resuspended itself for load almost instantly. The server load is extremely high at the moment, and you are one of the heavier users (your RAM use is consistently near 100 for the past several days) so it got suspended. I've put an htaccess with "deny from all" in your public_html to disable your websites, and unsuspended you. Please fix the load issue before removing it.

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. <br /><br />If you still see the suspended page, please clear your cache.<br /><br />If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic, you might want to consider purchasing a VPS instead. https://www.heliohost.org/vps/ VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access.

Ssl shopper is broken (probably a stale cache somewhere). That domain loads fine for me and has a valid certificate.

Unarchived. It should start working within the next 2 hours.

Unsuspended. In the future, you can just do it yourself here: https://www.heliohost.org/renew/

@troodber: See https://www.helionet.org/index/topic/40402-kill-python-processes/

Processes for user troodber have been terminated.

You're suspended for two reasons. First, you have two accounts when you're only allowed one. Your other account is yoe2006. Second, the content of this account violates our terms of service, specifically this line: Because of the smm panel and second account already being active, we can't unsuspend this account. If you really want to keep this account, I would need to suspend the other account yoe2006, then send an invite so you can create a replacement account for this one (which you'd never receive since the email address appears to be hosted on the other account...).

For mysql, you have to turn this on yourself in cpanel. There's a section for remote mysql where you need to add the IPs connecting remotely.

@Krydos: He likely said that because the wiki says 3.6: https://wiki.helionet.org/tutorials/django

I'm not sure what's causing it either...I would suggest you verify your contact info in cPanel though (and perhaps add a second email address). That setting is what controls the email addresses needed for password reset to work, so if the data in there is missing or invalid, it won't work right. The data in our other system was fine (which is where I got the email address to send a password to), but that system couldn't change the password for some reason (this not working is why our website reset didn't work for you). Nonetheless, if you're able to log back in, you should be good. Please let us know if you need anything else.

Manual password reset sent. Something is wrong with this account though, as it's not syncing correctly between our various systems (the server isn't talking to the account management system about your particular account for some reason). I had to go manually force a password change on it using a system we don't even usually use for password resets... Please let us know if you don't receive the email or if you need any further assistance.

Also, as someone who set up CF today, I found there is an option to remove the TLS 1.0 support on CF. It's under SSL on their site if I remember right, and lets you set the minimum supported version. Just set it to 1.1 instead. Anything made in the past 10-15 years will support TLS 1.1...

That link requires you to use your username. Enter sgorton1 as the username, then your email address when directed (it's a Hotmail address and will show a hint of which one it is). You must use the same email address you used when you signed up. If you no longer have access to that address, you will need to abandon your account and sign up again. We are unable to reset passwords if the email address on file is inaccessible.

Well, considering we recommend that people avoid both of those products, probably. CF is the more likely cause of that particular error though. That error is just saying there's support for old TLS (which CF has) though, it's not really an error so much as that service refusing to use older TLS to make a connection that's not as secure as newer technology. Step 1 is to remove CF and set your name servers to ns1.heliohost.org and ns2.heliohost.org. We are unable to provide support for websites that are behind CF because CF does all sorts of stuff to connections, and also hides the real DNS settings of your account.