wolstech

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.

The username is just atpray. Your last login date is today, so however you're logging in is working just fine. The cpanel login form can be picky though. The most common cause of it not working is the use of certain characters in the password. Quotes and spaces in particular are known to cause issues.

From what's above, he wrote junk code so bad that several of us have been left scratching our heads as to why it was written to begin with. I agree, he should take a vacation to Johnny until he figures out how to make software that isn't a memory hog.

This is the first time I've ever heard of someone trying to use RAM as file storage. Assuming you're using PHP, it should be automatically saving the files in /tmp if they're received via POST. You should be able to get the name from the $_FILES array. Use move_uploaded_file() to move it into your home folder, or unlink() to delete it. In order to do what you're doing, you have to either being cheating to send the files (i.e. not sending them as files but instead doing something like base64-ing them and shoving them into a normal POST field), or specifically make an effort to do something like using file_get_contents() on the temporary file. By the way, you just got suspended for this yet again. If you don't fix it quickly and it happens again, I'll put a deny from all in your .htaccess file so you can stay unsuspended with your site offline until you can rewrite this badly written file uploader.

Did you add the domain in cPanel under aliases?

Krydos is the only one who really knows anything about node...let's see if he knows.