wolstech

The heliohost.org login uses your account's hosting server to validate passwords. If your account is on tommy, it will say invalid because it's down. Users not on tommy can still log in through the website normally.

Tommy crashed due to hardware failure. Krydos is working on backing up the data so repairs can begin.

I noticed quite a bit of oddity after that reboot, the forum has been acting kind of odd as well (lots of things marked themselves as unread, a spam account unflagged itself...). Krydos might be able to fix this for you quickly, but be aware it may take some time because we're obviously more concerned about the data of the 1000s of users on tommy at the moment.

All DNS records can be served by any name server, so yeah, just move to NS2. Also, you've apparently learned why I hate FreeDNS...it's buggy and doesn't support multiple name servers. Their system is probably one of the few we hear a lot about when it comes to DNS issues. I'd suggest finding alternative DNS service if you can. CF does a decent job if you just use the DNS features (the caching and stuff works too, but there's some extra setup and considerations to keep in mind when you use those features here). Of course, the best choice is to just use our NS directly without a middleman, but we know that's not an option for everybody. CF is usually our recommendation when alternate DNS is desired, we've all used it at some point and the server can export the records directly to it with the plugin.

One of eddie's hard disks stopped responding and caused tommy to crash. That Eddie reboot announcement in the News section is related to the recovery efforts associated with the issue. Krydos is working on it...not sure if he plans to get the server online again, or if it's going to be converted to archives and be offered for download like the last few times this happened (Johnny has been through it 4 times, Ricky 1 time, but this is the first time for Tommy). The good news is that we already have a data center visit on our schedule for later this month, so replacing a dead disk will be easy and quick (compared to the last few times, where we had to wait months for the trip to replace it), if we end up needing to do so.

You can’t, which is why this is in the escalated bin. Krydos is the only one who does this, so you’ll need to wait for him to see the request.

That account doesn't exist, so it must have already been deleted.

Please fix or remove that script immediately. It caused several minutes of downtime on tommy. If you get suspended for this for a third time, you'll be moved to Johnny. Unsuspended.

Usually that happens when your network doesn't allow traffic on port 2083 (very common on work and school networks). Try a different internet connection (like a cell phone data plan) and see if it works.

Also, please be aware when you create a subdomain, it takes time to start working properly. Johnny and Ricky take 2 hours or so. Tommy can take longer.

This is not supported on our shared hosting, mostly in fairness to others also waiting for/using Java. Every war deployed causes additional load on the server, and allowing 2 wars would mean your account gets to hog a second slot that could otherwise be given to someone waiting in line. You could easily accomplish this on a VPS though. Tomcat itself is more than capable of it.

Please provide the transaction ID of the donation made for your invite so this can be resent.

Same issue as before. Please remove whatever software you’re using (I’m guessing WP, I can’t check from my phone) entirely. WP is notorious for this issue. If you get suspended a third time for this, it will not be unsuspended again until an admin deletes the offending software. Unsuspended.

Correct. Unless something has changed, you should never mark the posts in the email forum as solved. From what I was told, the post title is essential to how it tracks which email address the thread belongs to.

Krydos has to do this for you.

The templates should never be used in the email forum specifically because of that Solved flag (which breaks the email script). In addition, they don't work on mobile. I don't use them elsewhere too often either, but that's more because I usually want to include details specific to the case and it's easier to write my own post vs. use a template then edit it.

Sometimes this happens. It's usually our website having issues. Try using https://ricky.heliohost.org:2083/ to log in directly instead of using our website. Note that this form requires you use dasmarcy as your username, not your email address. Also try using the password reset option on that page if necessary. If it still won't work, let me know and I'll manually reset it and take a deeper look. Finally, be aware that when your hosting server is down, our website will not allow you to log in since it has to ask the server in order to validate your password.

WordPress got compromised...WP is notorious for this sort of problem. It's well known for being poorly coded, insecure, buggy, and also very heavy on resources. It's the leading cause of hacked accounts here at HelioHost. WP itself is notorious for security holes, and many of the free plugins and themes available for it are actually disguised backdoors. When you unknowingly install such a backdoor, it notifies the hacker, who then uses it to compromise your account, typically so they can send spam or set up a phishing site. The best way to deal with Wordpress's security issues...is to not use Wordpress. Just about any other CMS available is more secure than WP. We usually recommend Joomla. It's probably the second most common CMS in use today and has almost as much content available for it.

What he meant is you're not allowed to have a second account at all. Creating a second account will result in suspension for violating the TOS. You won't be able to create the second one anyway because the domain can only belong to one account at a time. The second account will fail to create due to the domain being owned by another user (your current account). If you try to work around this, you'll find it impossible to get your content to show due to the domain not being attached to the account (it'll be permanently queued). To be honest, Tommy's uptime is pretty good such that I never bothered to do this in the 8 years I've been with HelioHost. I run 3 production websites on him and see maybe a few minutes of downtime per week, mostly in the early morning hours (at least it's early morning EDT...)

Done. You can now log in, and your website will start working whenever Apache next restarts (probably within the hour since I manually requested it to restart). You may need to flush your DNS cache as well since the IP address of your account has changed.

Done. You should now be able to log in and your website should start working within 2 hours.

Yeah, the "send to new server" step is done, and the "receive on new server" part takes some time to move, it's 71% done...

Yeah, Youtube downloaders generally don't work well here. These and proxies are the top two load causers, with Wordpress being a third.. They use way too many resources, and if they don't just time out, they end up earning the user a suspension for load instead. The best solution here is to not host a Youtube Downloader.

Unarchiving... Also, your username is xlory061.

Moving...