Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


badrihippo last won the day on January 25 2014

badrihippo had the most liked content!

1 Follower

Profile Information

  • Gender
  • Location
    Thekampattu, Tamilnadu, India
  • Interests
    Programming, Writing, Environment, Reading, and lots of other stuff besides :)

Contact Methods

  • Jabber

Recent Profile Visitors

1,730 profile views

badrihippo's Achievements


Rookie (2/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges



  1. Awesome! Looking forward to Plesk and Morty too (well I'm not going to use them since I have a VPS, but still feels good to know it's there 😁). My VPS had become pretty slow during March/April but now it's back to normal, so I guess this reinforces that stable feeling. My team has been hosting our main website on Netlify till now, and we're planning to switch to a full-fledged Ghost on a HelioHost VPS, so the timing couldn't have been better 🙃 Re the reboot: nginx and some other services failed to start for some reason, so I had to SSH in manually and start them. In case anyone else ran into problems, the solution is to run `systemctl status service` and then `systemctl restart service` where service is the service name, such an nginx (web server), mysql (database), postfix (email sender), dovecot (email receiver), etc. Of course Hestia might handle all this by itself; I'm not sure (I use YunoHost) 🙂
  2. I haven't used Hestia, but from what I can make out, there's a cron job that automatically tries to run `v-update-system-hestia-all` every so often. I'm guessing it's some sort of auto-update command for Hestia. If it's timing it out means Hestia wasn't able to auto-update but I'm not sure why that could be. Does Hestia have a manual "check for updates" options somewhere? If so, you could try running it and see what kind of error it gives (if any). Not sure about avstats (or did you mean awstats?) because I haven't used it. What is a download list, exactly?
  3. We aren't switching the hosting company exactly, but cPanel revoked all our licenses without warning so the control panel has to be moved over to Plesk instead. Until this happens, nobody will be able to sign up or access their existing account, and the free websites will go down for sometime in the middle while the switchover is happening (this could take weeks because HelioHost's scripts are very tightly integrated with cPanel and a lot of them will have to be rewritten to work with Plesk). You can find the full story here: Later updates will be coming on the News channel: https://www.helionet.org/index/forum/1-news/ Unfortunately, until the switchover happens, you won't be able to sign up for a free account. You can still sign up for a paid VPS since those don't use cPanel and aren't affected by this sudden change. When the switchover is complete HelioHost will probably keep free signups suspended for a little while to make sure existing users have their setup running smoothly and then open up again for free signups. (By the way, I'm not sure what you can do about your display name but one of the mods can probably help you with that).
  4. Awesome! Great to hear and glad I could help 🙂
  5. No problem! If your provider asked for two DNS servers I suspect you'll have to go for my backup option: managing DNS externally using a service like ClouDNS to register A records, then adding the domains to Hestia to use them. (Even before Hestia is set up, you'll know the DNS is working because you'll be able to SSH in using ...@yourdomain.lu instead of ...@some-ip-address). You're right, though, Krydos might have some better ideas...
  6. That isn't what I had in mind, but I went through the Hestia docs just now and realised what you're proposing is a better solution. Sorry about that. Some explanation is probably necessary here. Explanation of how the DNS system works I should probably start by saying I'm not completely sure of the nuances of the system either, but I have messed around with DNSes quite a bit. What follows is my understanding plus a few educated guesses and some StackOverflow searches. If everything goes smoothly, you may not need to know all this, but when I got stuck (which was not uncommon) it helped me to know all this and have some idea of what was going on! There are three components to this: Your registrar, which points the domain to a nameserver. For example, I have snipettemag.com pointing to the nsone.com nameserver, which is what I use. So if anyone wants to load snipettemag.com or its subdomains, they're told to look it up at the nsone nameserver. Your nameserver, which actually manages the domains, subdomains, etc. and redirects them to the respective machines. For example, snipettemag.com points to a Netlify server but stats.snipettemag.com points to my VPS and media.snipettemag.com was until recently pointing to Tommy, where I was storing images and other static files. The actual server (VPS, Tommy, etc) which receives the requests and responds appropriately. For example, my VPS is set up so that stats.snipettemag.com serves a local GoatCounter installation I have, whereas bag.snipettemag.com redirects to my Wallabag. Both requests come to my VPS, but the VPS responds differently based on whether the request is to the "stats" or "bag" subdomain. You wouldn't have seen these moving parts on Tommy, because HelioHost runs the nameserver as well as Tommy, so the two are well integrated. When you add a domain (or subdomain) to Tommy, it automatically creates the corresponding DNS record as well. On other setups (such as mine) it's more common to run the server by oneself but delegate the nameserver to some other provider. The reason is that if your VPS crashes, the nameserver will go down as well, which means any other domains it serves (eg. email or an external subdomain) will go down as well. The downside is of course that you have to register domains twice: once on the nameserver end, and once again on the server (think one to send and one to receive). This setup is what I was trying to suggest for you as well. My recommendation for you But now I realise that Hestia has a DNS management facility. If you're just going to be hosting one domain, and Hestia handles it without much advanced setup, then maybe that's a better option for you. In which case the answer to the first part of your question is yes: your VPS is the "real nameserver". The problem is, you'll have to point to it using an NS record, which StackOverflow tells me needs a domain name (not an IP address). I think you can solve this problem by registering two records at your provider's end: an NS record pointing [yourdomain.lu] to [ns.yourdomain.lu] an A record pointing [ns.yourdomain.lu] to [your VPS IP address] That way you theoretically have two servers—the nameserver ns.yourdomain.lu and the actual yourdomain.lu—which makes the DNS system happy even though they're physically on the same machine. This is assuming your provider allows you to add both NS and A records. (If not, you'd have to go for a separate nameserver like ClouDNS, and update the records there as well as in Hestia every time you want to change something—which is hopefully not often). I'd like to signoff by saying that I've never used this kind of setup, although it's what I think would work best for you. I'd suggest you give it a try. If it works, then great; if not, I can't help you, but I'd be happy to help out with setting up an external nameserver like I mentioned in the last line or perhaps someone who's more knowledgeable than me could step in 🙂
  7. What domain are you using: is it a HelioHost-provided domain or your own one? If it's your own then you don't have to wait for HelioHost to delete the Tommy DNS records: you can just change the settings at your DNS provider's dashboard. For example, I got my domain "sssnet.tk" on Freenom so I can log in to Freenom's control panel and change the domain settings there. Just create an A record pointing sssnet.tk (for example) to your VPS's IP address (which you should have got in an email from Krydos once it was created). If the DNS record is pointing directly to your server, then any obsolete HelioHost records will be bypassed because requests will go directly from your new record to your VPS. The basic DNS record types, which are available at most providers, should work for you. But if at some point you want more advanced DNS records (say, for an XMPP server) then you could sign up for a dedicated DNS host such as the freemium ClouDNS. Security is a much more complicated business: I use YunoHost instead of a control panel, which automatically installs firewalls and monitors like fail2ban. I'm not sure if Hestia has its own security in place, but one thing you could do is change your SSH port to a non-standard one. I used to get a lot of random people trying to log on to my VPS on port 22, and now that I've changed the SSH port it doesn't happen any more. But I'd suggest you play around with the server a bit and become more familiar with it before you try this 🙂
  8. One more from Tamil Nadu, India, Asia 🌏
  9. If you want to gamble on Tommy being back in a month, perhaps you could sign up for a one-month trial at Linode or some similar service? They provide pretty decent VPSes. If it's a long-term open source project, you could also apply for free hosting at Fosshost. I'm not sure how strict they are, but it might be worth a shot. I don't think they're interested in short-term operations though, and there's a submission process you have to go through. I've also used Byethost in the past; they have a cPanel-based setup although it seemed slightly shady and they try to push you to upgrade to Hostinger, whom I think are their partners. Speaking of which, if you're willing to spend a couple of dollars just for the month, Hostinger has mildly restricted plans starting at $1.39/mo. Nothing perfect, but they might be able to keep you running till Tommy's back. Good luck!
  10. Yup, got it. The scalability factor makes sense; I didn't think of that! No worries about that: I have a (HelioHost) VPS already; just hadn't bothered to move the last few stuff from Tommy. I guess the time for that has come 😅
  11. Wow, thanks @balloons for the detailed response and for taking the time to piece everything together! Good to know about the timeline; I'm on Tommy so I'll start moving right away then 😛
  12. If you're a bit more adventurous, you could also try YunoHost: you need to copy-paste a few shell commands to set it up (and it needs a Debian VPS) but once that's done you get a dashboard to set up domains, email, SSL, etc., as well as the facility to install various "apps". Might not be for you if you're planning to switch back to Tommy eventually though.
  13. Hey there, Just got you email about cPanel unilaterally revoking licenses 🙁 Very evil of them, and thanks a lot for the heads-up as well as working so hard to keep this service going! A few questions about the switchover process. Others are welcome to add in theirs too—I see queries all over the place right now and it'd save time for everyone if we had everything in one thread (the more generic ones, at least) 🙂 You say our websites will be down, but as of now mine (a set of static files as well as a MySQL remote connection) are still working. Does that mean it'll stay, or is it going to go down in a bit? If the latter, would there be a grace period before you start work? I'd definitely find it helpful if I had, say, a couple days to switch over to my VPS and get things running there. (Of course that also means people who don't have a backup plan wait that much longer for their setup to be fixed, so if you need to blackout now, that's cool, I understand). A more long term question (which you've probably already thought about): are there any open-source cPanel/Plesk alternatives which would prevent HelioHost from being caught in the cold again? Also, to answer some of the panicked enquiries elsewhere on the forum, I'm pretty sure HelioHost will remain free as soon as the Plesk switchover has been sorted out. That's kind of the point of their existence 😉
  14. This is not a specific issue but a general question. Is there a way to manually reboot my HelioHost VPS without contacting customer support? I know I can just type reboot in the console to have it restart, but I'm talking about cases where the command line is inaccessible, for example because of high load or an out-of-control process (which happened to me recently). It would be nice if there was some way to expose the vmware commands for a hard power-on/power-off—not that I would use it much, but it'd be a safety net I'd know was there if something went wrong.
  15. Thanks! The runaway process must have taken over again when I checked, because I wasn't able to log in or even ping, but it's stabilised now and I have some inkling as to what the problem was. (My YunoHost had many dyndns processes running; I'm not sure why but I removed the DynDNS domain name since I don't use it anyway). Do you think there's a way you could provide "hard reset VPS" buttons to users? Just for poweroff and (re)boot. I think it would make things easier, because (a) I won't have to worry about powering off the system in such a way that I can't turn it on again and (b\) if some memory situations happens I can reboot myself instead of having to ask each time. I'm not sure how that would work in your setup though, but maybe you could have an email-based API or something that pushes the vmware buttons internally?
  • Create New...