Leaderboard

Less than 24 hours later we have already managed to negotiate and sign a contract with Plesk that is even better than the one we had with cPanel. It's going to be a lot of work to rebuild everything with Plesk, but in the long run this will be a good thing to get rid of cPanel. Plesk can run on Windows and Linux so we will be able to offer a unified system that includes all of our existing Linux servers as well as our Windows server Lily. Since Lily will have a real control panel it will make it much easier to create an account on her and give easy access to many more people to develop their websites for free using Microsoft's ASP.NET. Plesk is excited to be given the opportunity to supply the control panel that we use to provide much needed assistance to thousands of students, the underprivileged, and small businesses around the world that cannot afford to pay for hosting. Part of the contract includes our permission for Plesk to feature our logo, our mission, and our success stories on their website. Honestly, we couldn't have even hoped for something more perfect than this. It's going to take some time to get everything switched over though. Now that we have a new contract for a control panel our next highest priority will be backing up everyone's account. Then we will wipe Tommy and rebuild him using Plesk, and begin restoring accounts. After that will be Ricky, and Johnny. In the meantime you might consider a VPS to keep your site online using the same domain that you have now. You can find the VPS signup page at https://www.heliohost.org/vps/ Let us know if you have any questions or need help with anything during this painful transition. Thanks for being a member of the HelioHost community.

.NET requires Windows, so no it won't run on Tommy (which is linux). We do have a Windows server (Lily) which we hope to also have running Plesk at some point and which should support ASP.NET, though having started to dig into it, that I'm not sure it's as feasible as Krydos thinks it is (as I discovered through research, Plesk apparently "cheats" in a lot of ways when run on Windows...). EDIT: No we don't accept cash app. We accept paypal, skrill, and various forms of cryptocurrency. See https://heliohost.org/donate/

Thanks! Also, for those who do need features not on our free shared host offerings (like shell access or the ability to run custom apps like a game server), our paid VPS offering starts at only $4/month too, much cheaper than GoDaddy, whose closest comparable VPS is almost $20/month. We're planning to upgrade our servers in the near future too with additional capacity, and down the road after this cP/Plesk fiasco blows over we hope to offer an ultra-low-cost paid non-VPS option as well.

You have to realize that the purpose of most hosting companies is to make as much money as possible. They know the same thing we do, that Wordpress causes insane amounts of load, but rather than suspend people for it they try to milk the situation for as much money as they can. Rather than tell you how much load you're causing and trying to fix the problem they do stupid tricks like making their free hosting unusable to force you to upgrade to a paid plan. Seriously, every website should have SSL in 2021. The only reason to not provide free SSL is if you're trying to force people to upgrade to a paid plan. HelioHost's main purpose is to provide free hosting to as many students, the underprivileged, small businesses, and everyone else that can't afford paid hosting. We try to be as honest about everything as we can be, and we definitely don't play any tricks to try to force you to upgrade.

What @infantex said is exactly how its done by pretty much all. For example, even heliohost.org itself works like that (where the name server ns1.heliohost.org is a subdomain of the domain being configured). The IP address of a valid name server for the domain is needed at the registrar ]when the NS points to a subdomain, just so DNS has an idea where to start looking. These records are known as a "glue record", and internally are just a plain A record. If you're curious about the logic behind it and why you need to set up your DNS this way when you host your own name server on your VPS: https://ns1.com/blog/glue-records-and-dedicated-dns

What I did, as per @wolstech suggestion, was to add, at my registrar, my own site as DNS. As you mention, my registrar required that the DNS be a domain, so I entered: "ns1.infantex.com.mx" (infantex.com.mx is my domain). I guess the registrar detected I was using my own domain as DNS and enabled a field where I could enter the VPS's IP (@wolstech referred to this as "glue"). Try it, it should work. EDIT: I forgot, you need two DNSs. I don't know if you could enter ns1. and ns2.yourdomain.com, both with the same IP. 🙂 Or use some third-party DNS as the second one (Cloudfare, ClouDNS, ...). I haven't used them.