wolstech

That account cannot be unarchived because you already have another account. Users are limited to one account. If you would like to restore bharatp, the account bharat0 needs to be deleted first. If you would like the contents of that account sent to you, please let me know and a link to the archive can be sent to the email address on file for the archived account.

Please post the actual domain that doesn't work so we can assist you. The most common cause though is that people don't realize they actually need to register the domain. You need to actually go to eu.org and register it. Once you do that, use their website to set the name servers to ns1.heliohost.org and ns2.heliohost.org. Note that they can take several hours or longer to update once you set them. Entering a domain on our site during signup does not automatically register the domain, it only tells our system which account to look at for the content. The only domains that will work without the above steps are subdomains of heliohost.org.

Nope. Only the main cPanel account will work on SFTP. Any FTP user created in cPanel must use unencrypted FTP on port 21. You're not blocked on my end, so I'm not sure why you're getting a block message either...perhaps someone already unblocked you?

That domain isn't even registered. You need to go over to eu.org's website, register the subdomain, and set the name servers to ns1.heliohost.org and ns2.heliohost.org.

Done. It should start working shortly (as soon as Apache finishes restarting).

Unarchiving...

As described by one of our users in a previous response, Java is assigned automatically. We do not offer any way to skip the queue, and the wait (especially on Johnny) can be a month or more at times. As of this reply, the estimate is showing July 28th. You will need to keep your account active and be patient until you receive access. Note that the wait shown is usually a worst case scenario and most users receive it sooner than the date shown. If you need Java sooner, moving your account to Tommy can shorten your wait. The wait on Tommy is only about 7 days at the moment, as opposed to 25 days on Johnny.

We do not allow more than 2 server based crons. The reason for the policy is both security and load. We've had people misuse the cron daemon in the past to run shell commands because we don't allow shell access. Limiting it to 2 commands per day prevents users from using crons in lieu of the blocked shell access.Server-based cron also uses significantly more resources than a web-based cron, because a web based cron is run like any other web page and therefore restricted by the resource use limits like max execution time that we set on accounts. A server-based cron is not subject to these, and consequently can let users do things like leave stuff permanently running on their account, hogging resources. Since you share a server with thousands of other people, it's not fair for one user to be hogging everything and making everyone else's stuff slow down.

Are you a VPS user? If so you should have root access to your own VM. If you're on our shared plans, this is done through cPanel: https://wiki.helionet.org/Installing_an_SSL_Certificate_with_ZeroSSL (The guide was written using Tommy as an example, but the procedure is the same on all servers). Automatic renewal of Let's Encrypt certificates is not supported on our shared plans. If you need self-renewing SSL, you should move to Tommy or Ricky where we offer AutoSSL. AutoSSL automatically generates, renews, and installs a valid SSL certificate for you. It uses Comodo as a certificate source instead of LE because of LE's extremely low weekly limits, but is otherwise functionally identical to a private server using an Acme client with LE.

That account has been manually unsuspended.

Please try signing in here: https://johnny.heliohost.org:2083/ instead of using our website. If that doesn't work, rest your password here and try again: https://johnny.heliohost.org:2083/resetpass?start=1

Please try signing in here: https://johnny.heliohost.org:2083/ instead of using our website. If that doesn't work, rest your password here and try again: https://johnny.heliohost.org:2083/resetpass?start=1

We don't even own Sparkie yet, and when we do finally get him, our plan is to rebuild an existing server on the new hardware. Sparkie is replacement hardware so we can retire the ancient, slow Stevie hardware that is currently Ricky's home, with some extra capacity so we can do things like sell VPSes.

The domain script doesn't work for Johnny users, and heliohost.org subdomains have to be your primary domain unless an admin creates it for you. I'll manually change this when I get a moment.

Perfect. Your account has been unsuspended. Give it an hour or two for the domain to start working and you're good to go I apologize for the inconvenience.

It's suspended because we just need a little more information. What do you plan to host on your account?

You cannot receive two storage increases as a result of donation, so no additional space. 2GB is the maximum space allowed per user (though exceptions exist, for instance we've offered space as a prize for contests...the prize is awarded even if you already have 2GB resulting in you having more than that). You will receive the inactivity immunity though. $1 per month. We typically prefer a recurring $1/month donation so it calculates nicely into our monthly goals vs. a single large donation that boosts one month (since people tend to not donate if our goal for the month is reached already).

This is by design to help keep load low and cannot be disabled. Properly written code should not need a lot of connections anyway. The limit is 6 for Tommy and 3 for the other servers, per user. If your code is well-written, it will open and use the same connection for the duration of its run, and close the connection as soon as it's done with it, so you shouldn't ever hit this limit because the connections only exist for a fraction of a second while the script runs.

I'm not sure what software you're running (though I'll commend you for not using Wordpress ). Please fix this issue quickly since it impacts others on the server. Unsuspended.

Both of those are extremely bloated and slow. The main difference between those two, is that Drupal is more secure than WP and less likely to get hacked. Joomla is an alternative that isn't too bad, but it's still quite a bit slower than some of the bare-bones CMSes like Anchor that run quite well. The issue with these is that they need tons of resources and time to generate pages. A lot of the errors you see with these programs are because the scripts time out. We have a cap on execution time to help keep it fair for everyone, and the servers we have are not that fast.

That’s usually due to forgetting to change file permissions to 644. In some cases it can also be invalid htaccess files or just invalid code.

This is working again.

This appears to be fixed.

Services like easy cron are allowed. It's only cron scheduled through the cron scheduler that's limited, and that's for load and security reasons.

Tomcat is running again. Did your deployment process?