Krydos

Each domain that java is enabled on increases the total server resources that are required by tomcat. If we were to enable java on two of your domains then that would essentially mean someone else wouldn't be able to java enabled at all. By default your main domain is the domain that java is enabled on.

For people who search and find this you can change your own password at https://www.heliohost.org/reset/

How long does the script run for?

If you log in at https://www.heliohost.org/login/ this won't happen. Unblocked.

That .war file cannot be deployed due to errors. 07-Dec-2017 17:28:38.391 SEVERE [localhost-startStop-2] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cuzinsws_cuzins-web-service-1.0.1]] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:158) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NoClassDefFoundError: javafx/application/Application at com.cuzins.web.Main.configure(Main.java:18) at org.springframework.boot.web.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:121) at org.springframework.boot.web.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:87) at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:169) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5167) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:152) ... 10 more Caused by: java.lang.ClassNotFoundException: javafx.application.Application at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1284) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1118) ... 16 more 07-Dec-2017 17:28:38.391 SEVERE [localhost-startStop-2] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive /opt/tomcat/apache-tomcat-8.5.4/webapps/cuzinsws_cuzins-web-service-1.0.1.war java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/cuzinsws_cuzins-web-service-1.0.1]] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 07-Dec-2017 17:28:38.392 INFO [localhost-startStop-2] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive /opt/tomcat/apache-tomcat-8.5.4/webapps/cuzinsws_cuzins-web-service-1.0.1.war has finished in 13,600 ms

I would suggest taking a look at your raw access logs which can be found at https://tommy.heliohost.org:2083/frontend/paper_lantern/raw/index.html Keep in mind that 2017-12-04 is the day you were suspended so I would start there and look backwards.

We automatically post our news to facebook using a service called https://zapier.com/ Check them out. It's free.

I'll save you the time: https://web.archive.org/web/20170426212922/http://internetmoneyscam.com/ and https://twitter.com/idiotwhoreass Looks fine to me. Unsuspended. If you're worried about load check in here every once in a while to ask what your load looks like. We can run a report for you to let you know how likely you are to get suspended. We do have to suspend high load accounts occasionally to keep the servers from crashing, but it's usually not due to high traffic. Poorly written code and obvious abuse go first.

You'd be surprised how dumb some of these criminals are. We've actually had them create the domain phishing.heliohost.org, etc. Why did your site get taken down?

I restarted SFTP on Tommy. Is it working for you now?

You were suspended for high load on 2017-12-04. You were #1 for cpu usage, #7 for memory usage, and #151 for bandwidth. According to the logs the majority of your load appears to be coming from /home/seslaks/public_html/enkidu.org/index.php Which appears to be a wordpress install. You've got something pretty seriously wrong to be causing that much load with basically zero traffic. For instance there is someone doing 20,874% more bandwidth than you, and your account is using 4800% more cpu. I would disable all of your plugins first. Vanilla wordpress shouldn't cause this much load.

Your account was archived because you haven't logged in for several months. 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... Done. You should now be able to log in and your website is working again. http://stunning.heliohost.org/

Most of your load appears to be coming from /home/bh7/public_html/get.php

There are two ways to move your account as explain on our wiki http://wiki.helionet.org/Moving_your_account To move your account yourself you will need to delete your Ricky account before you create your Tommy account. If you want an admin to move your account for you do not delete it. Just create a backup and download it to your home pc in case something goes wrong.

Unfortunately you picked the only server we own that doesn't have java on it. We recommend Tommy for java as the wait to receive java is generally only a few hours. The wait to receive java on Johnny is several months. Let us know if you need help moving your account.

You were blocked for trying to log in to FTP too many times with the wrong credentials. Please verify that you have the correct information saved in your FTP client. Unblocked.

Your account was archived because you haven't logged in since August. 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... Done. You should now be able to log in and your website should start working within 12 hours.

Persistent connections https://dev.mysql.com/doc/apis-php/en/apis-php-mysqlnd.persist.html are mysql connections that you don't close. The advantage is that you don't have the overhead of creating and destroying connections. The downside is you use up one of your limited mysql connections and others who share your server suffer from degraded performance due to you hogging resources. As such we highly recommend closing your mysql connections.

162.158.91.232 was blocked due to failed cpanel logins as well. Unblocked. 162.158.92.69 was blocked due to failed cpanel logins as well. Unblocked.

When I hit that same limit I found a creative way to create a hash of the index column instead of the index column itself. It works much better than reducing the server performance by changing default settings. Check out something like http://mechanics.flite.com/blog/2015/06/09/hash-based-workarounds-for-mysql-unique-constraint-limitations/ As far as the max_user_connections, are you using persistent connections?

It already is unsuspended http://igwl.heliohost.org/ , and stop posting on other people's topics.

Your account has been manually unsuspended. If you still see the suspended page then you should try clearing your browsers cache.

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

Create the subdomain tomyself.icedcup.heliohost.org

As long as you close your connections each time after you're done with them you should be fine. We have websites with thousands of visitors and they don't get that error except rarely during high load. It's actually 6 now. One of the perks of being on Tommy instead of Ricky or Johnny.