wolstech

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.

You can renew a Lily account just like you would any other account. The only difference is that Lily can take up to 15 minutes to unsuspend after you renew it. Also, unlike the cPanel accounts, a Lily account doesn’t send an alert itself. If a CPanel account goes inactive or gets suspended, Lily follows very quickly (within minutes).

WHM is for root admins only. There is no way to give additional users access to an account aside from FTP. You best bet is to install whatever software you plan to use for your site then just let them have access to that.

Did you accidentally let your Johnny account go inactive at one point? I just unsuspended it, give it a few minutes and it should start working again.

Unblocked. It may take a few minutes to be effective. It was for failed SMTP logins, so you have a mail client set up wrong somewhere.

The domain http://colouringbook.ga/ is working for me. Please keep in mind though that video hosting scripts generally won't run well (if at all) here because of disk space and resource limitations though. If you're seeing a 500 error, high load is probably the cause. The error you posted above is erroneous because an index.php does exist in that site's document root.

I would suggest you try changing your password, then see if the new password works. It sounds like something might not have synced when your account was set up.

@Seekier: Game servers themselves are not, but websites for game servers are welcome so long as they aren't those nonsense "free skin giveaway" sites (which are actually phishing in most cases). I don't see the error OP mentions though...I get a blank white page.

File needs to be in cgi-bin as well. If it's not, you need to enable CGI in whatever folder you use with .htaccess.

As for the CF issues, please keep in mind that we don't officially support any configuration involving CF, as it's known to break many of the features in cPanel. AutoSSL and CF's full SSL are incompatible with one another because AutoSSL will not be able to renew its certs from behind CF's forced SSL connection. The "Full SSL" on CF does require a valid certificate be installed though, and in my experience the CF origin certs are hit or miss. Yours seems to be working, so you're good. AutoSSL won't attempt to replace a manually installed cert as long as it's valid. Finally, one thing to keep in mind, any time you install SSL certificates, it can take up to 2 hours for them to work (Apache has to restart), and you may also need to clear your cache if there was an expired one you replaced.

You already should get an email when the account initiailly goes inactive. Since you use gmail, it will be in your spam folder (Gmail considers all HelioHost mail to be spam because our servers are often abused to send phishing mail). If you find and "Not spam" it, you should get them going forward.

That error is because that domain is set as your main domain. You cannot add a domain as an addon when it's already your main domain. I've verified the DNS for your domain is correct. Please remove CF and set your name servers at your registrar to ns1.heliohost.org and ns2.heliohost.org, and it should start working. We do not support using CF, and because it hides the real DNS records from our testing tools, we cannot provide any further assistance until CF is removed and the name servers are pointed to us.

Your account filled up /tmp yesterday, which caused downtime for everyone else on the server. Something on your account is not cleaning up after itself like it should be. Did you upload a large number of components for Joomla through its web interface by chance (I've seen Joomla leave stuff behind if something like installing a theme fails)? Unsuspended.

Unarchived.

Unarchived.

Please set your name servers to ns1.helihost.org and NS2.heliohost.org. By design, our system will not allow users to add domains that aren't pointed to us as addon or parked domains. Once the domain sets up and is working, you can set CF up again. If you are unable to remove cloudflare for some reason, you will need to make this your main domain using this script: http://heliohost.org/classic/support/scripts/domain

Unblocked. It may take up to 10 minutes to be effective. It was for failed cpanel logins, if you use https://heliohost.org/login/ this won't happen to you.

Please check your PMs.

I'll send you credentials, you can't sign up for it yourself, and you need to keep the Johnny account.