wolstech

Oh, you're trying to separate the www. Yeah, you can't do that natively (though as you discovered, there's ways to do it by messing with the DNS after adding the naked domain). The www subdomain is a special subdomain in cPanel. It cannot be added manually because it auto-creates and is always supposed to point to the same thing as the naked domain it belongs to. cPanel always expects example.com and www.example.com to be identical because it's generally considered bad practice for them not to be (many people don't type www anymore, but some people still do, and as such by making this assumption, it ensures visitors see the same content regardless of how they approach it...if it didn't do this, most users here would have no idea how to set it up, or that they even need to). As you said, what you're trying to do is unsupported. The domain web.jbbdude.win cannot be fully cleaned up. Go ahead and give it a try, but the server did spit out an an error saying it cannot remove the zone from Johnny, so it might still fail. If that's the case, I'll put this in the escalated bin for Krydos to manually clean it up.

Tommy is not back. Your account is not suspended either, it's gone entirely due to the server rebuild. You'll need to wait until the rebuild is finished (there will be a News posting), then you can ask for an invite to receive a replacement account. If you have a Ricky or Johnny account, we'll be able to move that instead.

The IP of Afraid. cPanel won't accept sub-delegations. cPanel only looks at the FIRST name server in the chain (the GTLD's delegation response, which is usually the entries you set at your registrar), and checks its IP address. It does not follow the chain beyond that point, and could care less what the subsequent server tells it, because it never asks. cPanel queries root->gTLD servers, and the gTLD's NS records for your domain must be a server name that resolves to 65.19.141.3 or 64.62.211.133, or it fails. This check is not a HelioHost decision, it's a cPanel design decision. All cPanel hosts work the same way. Afraid is known for being incompatible with cPanel. Your solutions are: Eliminate Afraid and use us as your DNS provider.Use the domain in question as your main domain (the main domain doesn't have an NS check).Change the NS to us temporarily, let it propagate, add the domain, then change the NS back to Afraid and add the delegation.

Please clear your cache.

That inactivity message is because we deleted the account as part of the rebuild. That database was cleaned up last night. The login form won't show a maintenance message anymore because the system no longer knows you were on Tommy. It only knows that your account does not exist (which will display an inactive or non-exist message).

See sohamb03's answer. The accounts don't actually exist anymore contrary to what your domain is showing.

That account no longer exists. All Tommy accounts have been deleted because the server is being rebuilt. If you need your data, you can download your backups here: https://heliohost.org/backup/ After the repairs are complete, you can sign up again through free registrations, or if you're a donor, you can re-request an invite to get your account back.

I've used OpenManage Server Admin in the past on ESXi. It's been a while though since I've last had to set it up. Does the job quite nicely when used alongside the Dell ESXi image. OMSA would work on Sparkie if Krydos wanted to set it up since he's a PowerEdge, but Eddie is HP hardware (DL360 G6). The console commands for the tables in your last example are the only thing I've used recently. Proper redundancy is nice (and when I do servers, I do exactly what you said when I can...RAID 10 with a spare), but historically we've preferred capacity over reliability for cost and ad revenue reasons. It was only recently when we got the NAS that we got our first hardware with a proper RAID (I forget what type, I didn't set it up). Sparkie I believe was supposed to be configured as a raid as well (I think 10 was the preference, but we may have gone with 5). More often than not though, when our servers fail it's not hardware anyway, it's software corruption. cPanel was never designed to handle what we do to it. It's rated for a few hundred accounts (I think they say 400 max) per server, with the occasional create or delete. We cram well over a thousand in there (Tommy had around 2k when he died of disk failure, Johnny currently has 1500 active accounts, 10k if you count archives), and we're adding and removing users daily. In fact, cP themselves has admitted to us that we're the most extreme use case they have. Their support is always both dumbfounded and impressed that we've managed to make it work whenever we contact them (granted we do modify some parts of cP quite a bit to make it work, most of it is stock), then surprised when we tell them we give the accounts away for free on top of it all (they've given us tons of discounts for this...we're basically free marketing for cP). If anything, credit here goes to cPanel for a product that's well built to the point where can easily exceed its rated specs, and Krydos for spending all the time making it work!

Couldn't have said it better myself. The only difference is that the final step will likely involve signing up again or requesting a transfer (if you have a Ricky or Johnny account). There's no re-activating accounts because the accounts don't exist. He's seeing the effects of step 2 right now (OS/Software Install and Testing), and can just ignore what his domain shows until the work is complete. If he prefers I can remove the DNS records to get rid of the Index of / page for him. He will not be able to actually sign in until we announce the repairs are complete, he re-signs up, and the account creates.

Did you add that domain back to your account under Aliases? The DNS entries are missing and I don't see any sign its registered to an account. If you already added this domain to your account, try removing it, then add it again to recreate the entries. Self-signed cert means AutoSSL didn't run yet, or that it has failed to run. Give it 24 hours, and if it hasn't gone away by then, we can manually run it for you.

You're seeing that page because of Cloudflare keeping your DNS working during the server rebuild in progress. The account doesn't actually exist, and users using the recommended configuration would instead see an error message. There will be a news posting when the server is available again (I'd expect a week or so).

If you're on Ricky or Johnny, you can log in now. If you were on Tommy, you no longer have an account and should download your files: https://www.heliohost.org/backup/ Tommy users who donated for their accounts can request an invite for a Ricky account for the time being if they wish.

@sohamb03: That's what I get for a fast response. Fixed.

For JSP files, sohamb03 has the solution. For WAR files, this configuration is not supported. You'd need to just put a redirect in the root folder to redirect into the (invisible) Hbitsinfo folder. A simple index.php file can do that. Place it in public_html, set permissions to 644, and it should work. <?php header("HTTP/1.1 301 Moved Permanently"); header("Location: /Hbitsinfo/"); die("Redirect failed"); ?>

Johnny's got something wrong with cPanel. I get to the login screen fine, but logging in with valid credentials redirects me to an error: Internal Server Error 500 No response from subprocess (cpanel (cpanel)): The subprocess reported error number 72,057,594,037,927,935 when it ended. The process dumped a core file. cpsrvd Server at johnny.heliohost.org I had to try 3 times before I could get in successfully. I'm guessing load related, but I'll let Krydos confirm that.

It failed because your main domain has leftover dns entries that need to be cleaned up. I'll do this when I get to a pc later this morning.

You have to visit at just after midnight UTC to get an account. The registrations are only open for a few minutes a day before filling up due to demand. At present, we only accept about 30 new users per day.

@Luigi: Please don’t post email addresses publicly. It attracts spam and may upset users, especially if they would rather keep it private. Also, do not ask for a different email address. If the address on file is no longer valid, the user simply can’t get their data and will have to start over for security reasons. Users are expected to keep a valid address on file and to update it when it changes.

"Roguitarie" (all hardware names have to end in "ie", all VMs end in "y")

You'll likely need to request moving them, as we aren't tracking who wants to move back, who even made a Ricky account, etc. Once Tommy is online again and public registrations open, feel free to ask to be moved back to Tommy.

That cannot be done without deleting the account and recreating it. Since the original username is not available, you can't get a home folder with that name.

Closing since I brought this up in an email-related topic. https://www.helionet.org/index/topic/36605-email-not-working-outgoingincoming-mails-are-not-being-delivered/?view=getnewpost

Ricky has quite a few issues at the moment mostly due to overloading. I'm getting emails from my scripts, but I suspect I'm not getting all of them (I can't check because half of my stuff won't even run without multiple attempts due to 500 errors). The support email on the forum relies on Ricky as well, and that's broken too. I can't even get account backups to work at the moment. If I request a full backup, it never actually makes the backup...

Ricky is rather overloaded at the moment: http://heliohost.grd.net.pl/monitor/ That's a lot of blue...

(XID 7mgec8) A DNS entry for robbiewolfe.heliohost.org already exists. You must remove this DNS entry from all servers in the DNS cluster to proceed. The domain robbiewolfe.heliohost.org and robbiewolfe.ca have been cleaned up. Invite sent.