wolstech

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

That account was involved in illegal activity and cannot be unsuspended.

I'll just unsuspend it for you. But yeah, it's not a good idea to use a public/school computer here. We can't tell legitimate students from bots. Unsuspended.

You're suspended for having 10 accounts. Can you explain why there were 10 accounts created in the same time frame from the same IP address (this is a common indication of someone planning to use our service for abuse, typically spam or phishing)?

You can only have one account. Having 2 accounts violates our Terms of Service. However, you can use an addon domain to create a second website on your existing account. To do this, you should first obtain a domain from somewhere (buy one, get one from freenom, etc.), and set the NS to ns1.heliohost.org and ns2.heliohost.org. After that, add the domain in cPanel, pick a folder to use for the content, and upload your website. If you want one of our subdomains instead of a regular domain for your additional site, create a subdomain on one of your account's existing domain, then let us know what you named the subdomain and what you want your .heliohost.org subdomain to be and we can add it for you.

Also, we usually recommend avoiding Wordpress if you can. Not only does it tend to cause load when used with lots of plugins, it's full of security holes too. WP is responsible for like 99% of our high load suspensions and a good chunk of our spam suspensions (typically when it gets hacked). Try removing a bunch of your plugins, or even better, find a replacement for Wordpress altogether.

It won't let you even attempt the addon domain if the subdomain exists, so you need to do the addon domain first and fix it if it fails. Easiest way to do it is to watch Johnny's load and do it when it's low (below ~12 or so) so it has a decent chance to work properly... The addon process is supposed to both parts for you (an addon domain is internally just an Alias parked to a subdomain, oddly the server parks the alias on the non-existing subdomain first, then actually creates the subdomain second...). The issue is that the subdomain part times out half the time due to load. You'd think it'd do the sub first and only finish the alias half if the subdomain actually succeeded...

Johnny is infamous for this crap. Since you already tried the subdomain (the usual fix), check to see if a DNS entry exists for that domain in the zone editor. If so, remove it and try again. This issue is the one reason I recommend people try and get a Ricky and Tommy account. Both of them work like they should and don't have these issues. I'll move this so Krydos can take a look as well. I was going to see if I could just re-park it on top of the subdomain for you, but Johnny's load is too high for WHM to even load

Added. You should now be able to edit the wiki.

You need to log into cPanel at least once every 30 days.

You're actually suspended for inactivity. Please make you use either https://heliohost.org/login/ or https://tommy.heliohost.org:2083/ (with nothing after the / ) to log in or your logins won't count. Unsuspended.

It was blocked for failed SFTP logins. Check your username and password in your ftp client. Unblocked.

What is your account's username and what server are you on?

To be honest, very few people here know Ruby, so you may not get a response. Our other root admin Krydos might know why this doesn't work though, so I'll pass this on to him to look at.

Deployed.

Correct, you should edit the context.xml that goes in your war, rebuild the war, and redeploy it.

Your path is wrong, the endpoint is actually at http://ds3cheatersblocker.heliohost.org/cridus10_ds3cb/getcheaters (the filename always goes after the main domain). It seems to somewhat work, in that it returns what appears to be empty JSON (just a [ ]).

Yeah, you can't drop it. Krydos needs to drop it for you. In the meantime if you want, you can create a new DB with a different name and restore the database backup into it.

Name servers are used on the domain registrar's website to point the domain to us. Did you register the domain? We don't register domains. Since you're using a .tk, you should register over at Freenom.com and sign up for that domain. During the process, there's an option to use your own custom DNS servers, and that's where you enter the nameservers.

That's a known issue caused by the limitations of Tomcat running in a shared environment like this. Some have managed to get this working by playing with the sessionCookiePath in context.xml or doing various other things (such as prefixing their war with username_ which is also required if WARs need to find resources packed inside them) but its hit or miss. We also don't have many Java programmers on here, so support for broken code is rather limited. Others have had issues with session-related code too: https://www.helionet.org/index/topic/32294-solved-request-for-war-file-to-be-deployed/?hl=%2Bjava+%2Bsession&do=findComment&comment=145801 (no fix found) https://www.helionet.org/index/topic/31718-i-have-uploaded-my-servlet-war-file-could-you-please-activate-it/?view=findpost&p=143545&hl=%2Bjava+%2Bsession (managed to get it working by messing with sessionCookiePath in his WAR's context.xml file)

That's because your username is ls, not lslab. Sign in here using ls as the username: https://heliohost.org/login/ The account exists and is working properly. Your domain is http://lslab.heliohost.org, and is showing an empty directory listing. As for the support email system...it has a rather strict spam filter and also discards any email containing attachments or pictures, so it probably threw your email away. You would receive a reply with a ticket number and link to the forum topic if it had accepted your email.

Lets see if our other root admin Krydos has a backup for it.

Deployed.

They were probably InnoDB tables that got lost during a crash a while back. This issue is why we highly recommend you use MyISAM whenever possible. We've lost InnoDB data countless times, but have never lost MyISAM tables in our 10+ years in operation. What's the database name containing these tables? We need that so we can check if a backup exists. Assuming we have a backup to give you (we attempted them prior to the repairs that caused the data loss but no guarantee they succeeded, backups are ultimately a user's responsibility here), you'll need to create a new database and restore the backup to fix them. Krydos can remove the current corrupt database if you wish as well, or you can just pick a different database name.

The domain attached to the account matching your forum username is working properly. If you see a suspended or queued page, please clear your cache.