wolstech

Those errors mean the app requires an older version of PHP. Find out which version it's supposed to use and select that version in cPanel under MultiPHP manager. My guess is that it's meant for 5.x. PHP 7 is not backwards compatible with PHP 5 and won't run most apps made for 5.

This is Krydos's territory. I don't know much of anything about Python...I'm a PHP guy.

It's suspended for both high server load and for having two accounts. The high server load is an easy unsuspension, but the multiple accounts is not. Users are only allowed one account. In order for me to unsuspend this one, your Tommy account needs to be suspended instead. Tommy is a much better server than Ricky, but your website is on the Ricky account. If you prefer, I can delete the Tommy account and move the Ricky account to Tommy for you. Which account do you want to keep?

He should be able to add those for you.

It got suspended because, historically, most (over 90%) of accounts mentioning amazon turn out to be fraud or phishing of some form. We can unsuspend you, but we need to know what exactly do you plan to use this account for?

You know the drill ...

Your domain has been changed and your account has been unsuspended. Please give the domain a few hours to start working.

Yep, I did...

Luigi got it right. You got suspended because that domain is a security risk (typo-jacking). Please pick a different domain and let us know what you want it to be. We will change your domain and unsuspend you.

Gone.

From June 1, 2017...no wonder we couldn't find it. Sent.

Unarchived.

Looks like it started moving again and is working through the backlog now... Weird, especially considering his load wasn't even high.

The account cannot be restored because the archive is missing. An invite for a replacement account has been sent to the email address on file.

Yep, typo. It was actually registered that way and I fixed it earlier, but had no time to wait for DNS to set up. It's working now: http://mybai.heliohost.org/

Please check your PMs.

The account nmesisca2 was suspended due to inactivity. I restored it and it should start working again within the next hour. Please keep in mind that renewing the cPanel account attached to a Lily account does not renew the Lily account. To restore an inactive account that has a Lily account attached to it: Renew the cPanel account if needed and confirm you can log into it.Renew the Lily account once the cpanel account is working.Wait up to an hour. Lily accounts don't restore instantly unlike cPanel accounts.

Johnny isn't setting domains up at the moment, or creating accounts, or doing much of anything config or maintenance wise. Until Krydos fixes this, this won't complete its set up.

Johnny's account management process seems to be stuck. Your account is one of 15 waiting to create at the moment, alongside numerous accounts that need to be suspended for inactivity or archived. Our other root admin Krydos needs to check on why this is stuck...

As flazepe said, you can't. We have to do it. Please keep in mind that we will not adjust many settings (especially the execution time and memory limits) because we restrict those to keep the servers fro being overloaded. Please specify the php version and which settings you need adjusted so we can consider your request.

Tommy is currently up. There was some load-related downtime earlier, but the server has since recovered from that. http://heliohost.grd.net.pl/monitor/

Lets have Krydos take a look yet again. The main domain isn't really a good solution since most users who use these free ones want to use more than one. It's getting old having to park these manually for people. With the .br it was never an issue because they were paid domains and most users only bought one. As I said above:

Invite sent, thank you for your donation.

We've been seeing this with a lot of providers lately. Krydos and cPanel's support are adamant there's nothing wrong on our end, but I personally don't agree. Every domain provider I hear about having this issue started experiencing it around the same time. I doubt they all changed their policies at the same time. Can you provide a few examples of domains you have set the name servers on but can't get to work? I think we need to start looking for an alternative to these name server checks to be honest. Allowing all domains that are unresolvable would be one option that would fix this, and still keep people from doing dumb stuff like parking google.com (it would always resolve to google, so would fail a check that allows unresolvable domains)

It can be manually parked, but we don't like doing so if it can be avoided since it's a pain and takes time on our part. Our official stance is that eu.org is simply not supported outside of the main domain. The country domains from Brazil (ending in .br) have the same compatibility issue for the same reason, nonstandard behavior on the registrar's part.