wolstech

That was abusive use, and two people did get suspended for it. The problem is that when the load is massively high like that, it can take a significant amount of time for the suspension script to actually work. On a normal day, suspending an account takes 30s-1m. When buried in load, that process can take an hour or more. Then there's the fact it's not always just one user needing suspension. Most of the downtime period is the time spent actually doing the work to suspend the user. Once that process reaches the point where it kills all the user's processes, that's when the account no longer produces any load, and the server load starts to return to normal. The give away of a severe high load incident on that chart is the almost instant cutoff from green to red where it goes down, followed by the load tapering from red back to green over a few minutes at the end of the event (as the abusive processes die).

You probably tried signing in when tommy was down last night. He was down quite a bit last night due to what appears to be high load but is now back up. http://heliohost.grd.net.pl/monitor/

You don't really redirect it so much as you just need to configure the domain to use our service for its content. The proper way to do this is to change the domain's nameservers to ns1.heliohost.org and ns2.heliohost.org (you do this on OVH's website, contact them for help if needed, we don't know OVH's system so we can't explain the process), then add it to your Tommy account in cPanel under the Aliases option (let us know if you need help with this step, we'll be happy to!).

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. <br /><br />If you still see the suspended page, please clear your cache.<br /><br />If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic you might consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator

You're only allowed to have one account. This one is suspended because you already have a tommy account jarsatu.

It looks to be available. I don't see it registered in the system.

Please don't advertise social media marketing services here. It will earn you a ban for spam.

Any update on this? I had someone PM me about it earlier this week, and another user I helped today is using it as well.

Yeah, this app is one of many solutions. Also, be aware that with the 2FA enabled, you might need to renew every 30 days (last time I tried, the 2FA kept the activity monitoring system we use from detecting logins, not sure if this has been fixed). For those who don't have a phone, WinAuth provides this functionality for Windows PCs: https://winauth.github.io/winauth/download.html It can be stored on a flash drive or similar for portability and to reduce exposure to malware.

I've technically been here 10 years, but have only active for 8 of them (I joined in 2009 originally, but my account expired from inactivity and I didn't return until 2011). I became a moderator in 2013, an admin sometime in 2015 or 2016 (I forget), and a root admin in 2018. You can PM me on the forums if you want to reach me privately. You can do that by pointing at my username and clicking Send Message.

WordPress gets hacked due to backdoors, malware, and poor coding, not lack of security features. It's primarily the extensions and themes that are the issue with it. Many of the free themes and extensions have malware built in. I've seen far too many WordPress sites in my 8 years with HelioHost that started sending spam or hosting phishing due to WordPress, and it always ends with the user getting a new account. And yes, if you get a lot of traffic, I would recommend CloudFlare to help with it.

WordPress tends to get hacked very easily, so we don't recommend it. If you a proper content manager, we recommend Joomla instead. It's more secure and provides most of the same features. Plain HTML is the most secure but least functional choice. If you use regular HTML, you will probably want to use a template or a desktop program like Dreamweaver to make your website.

Sorry about that. It suspended itself again for inactivity. I've been unsuspended rot8 and renewed it for you. Give it a few minutes and it should work as well.

Thank you. The accounts rot2, rot4, and rot5 have been unsuspended and should be available shortly. If your friends are unable to sign in, please have them clear their cache and/or reset their password. We hope you enjoy our services, please let us know if there is anything else we can help you with

The 2FA has been removed from rot1. Please try signing in now. In order to unsuspend the other accounts, we usually require a scan/photo of government IDs be submitted for each additional account to verify that there are actually several people using these accounts. We require a different person for each account, so for four additional accounts, I need to see the IDs of 4 different people. Each user should submit their ID using their own forum account so we can track whose account belongs to who (please PM the ID photos to me to keep them private, once verified we'll let you know and you can delete the pictures).

That account is not suspended. If you see a suspended page please clear your cache. If that's not the issue, what exactly do you need help with? Do you need your 2FA removed?

Unblocked. It was for failed IMAP logins, so you have mail client somewhere that has the wrong password saved in it.

Krydos never posted the finished message, and it's been almost 24 hours...it likely failed. Accounts usually don't take more than an hour to unarchive even when the server is slow. Let's have him look at it again. I don't want to unarchive it again if it's somehow still running because it'll just cause a mess.

Your trial is now a normal Tommy account and will no longer expire. Please be sure to log into cPanel via https://tommy.heliohost.org:2083/ (with nothing after the slash) or https://heliohost.org/login/ at least once per month to avoid inactivity suspensions. As long as you do this, you can keep the account as long as you wish. If you forget to sign in, you can renew your account from the inactivity page, or let us know and we can renew it for you. Thank you for the donation

That's possible. When we troubleshoot internal server errors, the first thing we do is rename .htaccess files and check the file permissions. I did both at once and didn't check the two causes individually, so it's possible the htaccess file is not an issue at all. If it works with the Joomla code in it, then you're good.

The source is usually the same for both versions. It's how its compiled that determines the platform. Honestly though, for testing the 32-bit version should work fine. The bigger issue is that nobody has actually fixed the bugs in the code for Windows (hence the App Data issue) since nobody uses Mono on Windows, so the odds of it compiling successfully on Windows are probably close to nil, let alone building from source actually working. The Windows builds for the actual server that I've seen online were actually built targeting Windows using a Linux box. If you don't know advanced coding, you likely won't be able to get this working. They're throwing errors because probably due to a path issue somewhere in your configs. You have to remember that Mono and Apache have different document roots and ports. For example, Apache and Mono need to both understand that a request for "localhost/aspxapp/test.aspx" is actually "localhost:2000/test.aspx" The easiest way to go about this is probably to cut out Apache entirely and just do the ASPX coding on Mono's server directly. A well-written program shouldn't need both anyway since it should all be in one language. You said you had to do ASPX for a specific reason, so I'd just use Mono for that purpose and leave everything else (PHP, etc.) separate. It will solve all of your issues except the App Data folder (which may or may not be an issue anyway, beyond the log errors). I ended up doing this when building our IIS server. It was supposed to be IIS behind Apache, but the Apache part caused so many issues it was determined to not be worth it and IIS is now just directly exposed online. Users who deal with Java have similar problems behind Apache, though for different reasons. I seriously don't recommend using Apache as a wrapper for other servers if it can be avoided.

You'd have to build it from source, which on Windows is often not easy. Linux is usually an easier platform for building stuff on because all the requirements are conveniently available as packages. Windows means running around and installing tons of random stuff and knowing how to configure it. If you're lucky, some programs will build in msys2 (Linux compatibility environment) which makes it a little easier. Windows 10 also has WSL, but that's cheating (it's just a Ubuntu Linux VM running in the background with a seamless UI). I can't find the answer for the app data folder. I suspect it may be built into the code that way and nobody ever bothered to update the code for modern windows. Back in the day, Mono sometimes found on Windows XP for testing because full ASP.NET wasn't available in workstation OSes (even though IIS was in XP Pro). With IIS 7 and newer (Vista and up), full ASP.NET is available on all non-Home OSes...which basically eliminated its use case for Windows.

More than likely mod_mono isn't passing something to Mono correctly, so a bug. I sometimes have the same issue when dealing with pass thru on IIS for things like Ruby on Rails. Starting the second server manually usually fixes it.

Tommy port is definitely 1342. If it says 1312, it's a typo on our part. We also support vanilla unencrypted ("plain") FTP on port 21. Some users have better experiences using that instead. Just be aware it's insecure. As for the 404 error, there's a ton of problems. First, your .htaccess file in public_html is preventing that from being accessible. Second, you forgot to change the file permissions. I've renamed the .htaccess in public_html to disable it and fixed the permissions on the emoticons folder and emot_box.php for you. You need to change your PHP files to 644, and all folders inside of public_html need to be 755. Once you do that, your scripts should work. I would also recommend figuring out what's wrong with that .htaccess file.

Unsuspended. There’s nothing more you need to do at the moment, just use your account normally.