Krydos

That .war file cannot be deployed because java is not enabled on your account. To request java simply go to https://johnny.heliohost.org:2083/frontend/paper_lantern/java/index.live.php and click Request Java. Please be aware that since you picked the Johnny server the wait to receive java is quite long. The wait to receive java on the Tommy server is generally only a few hours. If you're in a hurry to get your .war deployed we recommend switching servers.

hyper-design.ir is redirecting to hyper-design.heliohost.org because you're running wordpress and you have hyper-design.heliohost.org set as your wordpress main domain. You need to change the setting in wordpress: https://codex.wordpress.org/Changing_The_Site_URL

There you go https://krydos.heliohost.org/cgi-bin/modules36.py

That's a good idea. We'll keep that in mind as we continue growing and buying more servers. In the meantime you can use a free cloudflare account to serve static content while the server is slow and cloudflare also helps reduce server load as well as speeds up response times to most everyone worldwide.

You're on Tommy which offers instant domain activations. What this means is apache has to restart. A lot. You're on a server with thousands of other people and each time someone adds or changes a domain apache restarts, and each time apache restarts there is a lag of a few seconds where pages won't load for a bit. This is one of our main features of the server. We could reduce the restarts like Johnny or Ricky, but then domains would take hours or days to start working. We keep a close eye on the response time of Tommy though as he's our flagship server. For the last 4 hours his median response time has been .010 seconds, and his mean response time has been .143 seconds. We think that's an acceptable balance. If you want a server that only restarts apache for you and you alone you need to be the only person on the server. Check out https://www.heliohost.org/partners/vps for that service.

You were blocked for logging in to cpanel with the wrong username and/or password too many times. You can prevent this from happening by logging in at https://www.heliohost.org/login/ Unblocked.

There you go https://krydos.heliohost.org/cgi-bin/modules36.py

You got suspended for running a Facebook spam bot. Sending spam is against our TOS.

The timeout message happens once you're already blocked, so the failed logins happened before the timeout message.

It says failed SFTP logins. Unblocked.

The fastest way to upload files is to upload an archived tarball of the directory structure and files, and then extract it on the server. The slowness of FTP/SFTP/WebDAV/etc. is probably because of the number of files not the transfer rates. I just tested the upload/download speed of Tommy and he's right around 100 Mbit/s both directions. Is your home internet connection upload speed higher than that? Do you consider 100 Mbit/s slow? Also, a lot of developer tools like Visual Studio Code, Dreamweaver etc. that I've seen support differential file transfer anyways over regular (S)FTP. I would use rsync though if it were available, but as hard as FTP is for most people to figure out I doubt many would use it. I'm actually a little surprised that cpanel doesn't support it now that I think about it.

Your account was archived because you haven't logged in for three months. You can prevent your account from becoming archived again by logging in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving... Done. You should now be able to log in again at the above link, and your website should start working again within 12 hours.

Unblocked. Make sure you have the right username and password entered in to dreamweaver.

You might also want to check your spam folder and whitelist our emails. We sent you a warning email a couple days prior to the inactivity, and we sent a second email right when your account was deactivated. If you had received either of these notifications you could have prevented this downtime on your site. Both emails contain instructions on how to prevent inactivity, and reactivate an account once it's inactive.

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. If you still see the suspended page, please clear your cache. 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

What are you going to do to fix it?

There is no account with that username. There is no longer any server by that name. We now have Johnny, Ricky, and Tommy available for user accounts. The first step towards hosting that domain is to set your NS records to ns1.heliohost.org and ns2.heliohost.org on your domain registrar's website. Digging a little deeper it looks like you created your account keckge 2016-05-16, and then we decommissioned Stevie in December 2016. Your backup is still available at https://www.heliohost.org/backup/ Once you've downloaded your backup we recommend creating a new account at https://www.heliohost.org/signup/ Since you picked Stevie last time we recommend Tommy as it's a similar production style server with maximum uptime. Let us know if you need help with anything, and welcome back.

Apcu is a php module used for caching opcode. http://php.net/manual/en/intro.apcu.php This means that it can help your site run faster. That isn't actually an error. It's a warning which means it isn't critical and it isn't actually causing any issues. It's just warning you that the apcu module was already loaded once in your code, and then your code tried to load it again. Maybe you have the same line duplicated in two places. The warning just lets you know about it so you can fix it if you want to.

Unblocked.

I would say if you have a well-written site that closes the mysql connections immediately after the query completes you could have 100 simultaneous users at least without seeing that error. If the server load is higher that number will decrease, and if your code is poorly written you may only be able to have 1 or 2 users and you will see that error. It depends on a lot of things.

As this is the fourth time you've been suspended for high load, I would like to know what steps exactly you have taken to reduce your load so far?

Before you can deploy a .war file you must first go to https://johnny.heliohost.org:2083/frontend/paper_lantern/java/index.live.php and request java on your account. Please be aware that since you picked the Johnny server the wait to receive java is quite long. The wait to receive java on the Tommy server is generally only a few hours.

Mock 2.0.0 is now installed https://krydos2.heliohost.org/cgi-bin/modules36.py

You're on Tommy now. http://ilovehm.heliohost.org/ You can log in at https://www.heliohost.org/login/ It looks like you may have solved your load issues that got you banished from Tommy the first time, because you load on Johnny isn't bad. If you see a 404 error or a Johnny queued page please clear your browser cache and flush your os dns records. Thank you for you donation. We really appreciate it.

The .war deployment script is still in beta testing. Right now it's set really sensitive so it only deploys under the perfect conditions which sometimes don't happen very quickly. It also has hung up a couple times. I've got log files of everything it's been doing. I'm going to use the logged data to make some improvements sometime in the next few days. I can tell you right now that the changes I'm planning on implementing, if the filename remains the same as the previous deployment it will process it fastest. Some users change their filenames each time they deploy, example e2s-1.0.1.war, e2s-1.0.2.war, etc. Those types of deployments will take much longer to go through. Based on the log files you've been using the same filename each time so it should be quick for you.