wolstech

@BlueyEmperor: It won't. There's a flag on the user profile that will remember it. It appears to work because it logs you out when you dump the cookies as part of the cache clear. If you log back in, it will come back. The issue is usually triggered by replying to PMs on mobile.

We don't recommend WordPress for exactly this reason. It's really badly written internally, and as a result is notorious for high load (among other things...it also loves to get hacked, which usually leads to a ban for malware or phishing when the hacker sets up illegal content). The best solution to WordPress issues? Don't use WordPress.

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

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

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

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.

This is banned because it was imitating a bank to steal financial information. The referenced domain indsuind.com is attached to this account, and the mailbox is full of stolen bank information. We received the following complaint from RSA on behalf of the real bank this account is imitating. Dear Team, RSA's Anti-Fraud Command Center has been appointed to assist IndusInd Bank in preventing or terminating online activity that target, or may target IndusInd Bank's customers as potential fraud victims. We have detected that a recently registered domain, indsuind[.]com, which appears to be under your authority is involved in fraudulent activity targeting IndusInd Bank's customers. Please be advised that this domain is contains the name bank and now redirects to their legitimate website. We request your assistance in ceasing this fraudulent activity through any means available at your disposal. We would appreciate if you let us know once action was taken or if you were unable to take action. In case you require further information, please inform us. Regards, Anti-Fraud Command Center RSA Security, LLC., a Dell Technologies business UK Phone: +44-800-032-7751 US Phone: +1-866-408-7525 CA Phone: +1-800-406-8651 E-mail: afcc@rsa.com www.rsa.com 103 Needless to say this isn't getting unsuspended and cannot be backed up either. If you weren't the one who engaged in this illegal activity, a hacker got into your account and did.

Unarchived. It might take up to 2 hours for the domain to start working.

It's on Johnny. Unarchiving...

It's available on 7.3, but appears to be missing from all other versions. I wouldn't be surprised if this was intentionally removed though...we've had issues with this extension leaving behind large temp files that quickly fill up /tmp (which when full causes the server to go down).

Without an actual error message and the database connection settings you’re using, it’s difficult to diagnose anything. Can you post the connection code (edit out the password please)? What error message are you getting when it tries to connect?

It also was a federal holiday in the USA when you posted (where we are based)...turnaround on support requests for things that aren't PHP (and maybe Python) tends to be several days anyway, only one person here knows much of anything about those technologies. Most of us are PHP experts, and we have a few users who help with python stuff. I'm not sure anyone else on our servers is even using Ruby...it's one of the more rarely used features for sure. Krydos is the one who would be able to answer questions about this one... Also, I looked at that app, if it's just a fancy cron scheduler, please keep in mind that we have a cron limit of 2 executions per day.