Krydos

Your account was suspended because our systems detected that you might have more than one account. We understand that no one ever reads our terms, but as a reminder, our Terms of Service state that each user is allowed to have only one account. The reason we have to enforce this rule is because our servers are already overloaded the way it is, and it wouldn't be fair to everyone that is turned away each day for you to have more than one when so many others have none. One common reason people create more than one account is to get around our storage limit of 1000 MB. Did you know that we will give you another 1000 MB of storage for each $5 USD donation you make up to 5000 MB total? If you'd like to increase the storage of your account just make a donation and then let us know your transaction ID and username. Another common reason people create more than one account is to host more than one website. Did you know that you can host as many websites on your one account as you want? Unlike a lot of free hosts we offer unlimited alias domains, unlimited addon domains, and unlimited subdomains. If you need any help adding another website to your account just let us know. Another common reason people create more than one account is to try out several servers at once, or to transfer a website between accounts on different servers. Did you know that an admin can move your account for you for as little as a $1 USD donation? This will save you the trouble of signing up again, and deleting your account, etc. Sometimes our systems flags you as possibly having more than one account when you share a computer with family, friends, coworkers, other students, etc. If this is your situation we apologize for the suspension, and we'll be happy to unsuspend all of the involved accounts after you provide proof that each of the accounts belong to a different person.

If you can't change the nameservers you have to set it as your main domain.

org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [com.slimsimapps.ava.AvaApplication]; nested exception is org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'badLogController' for bean class [com.slimsimapps.ava.badlog.BadLogController] conflicts with existing, non-compatible bean definition of same name and class [com.slimsimapps.ava.BadLogController] at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:188) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:319) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:236) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:275) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:95) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:706) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:532) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:152) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:132) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:92) [spring-boot-2.2.6.RELEASE.jar:2.2.6.RELEASE] at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:172) [spring-web-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5196) [catalina.jar:8.5.24] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.5.24] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752) [catalina.jar:8.5.24] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728) [catalina.jar:8.5.24] at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) [catalina.jar:8.5.24] at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) [catalina.jar:8.5.24] at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) [catalina.jar:8.5.24] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_262] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_262] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_262] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_262] at java.lang.Thread.run(Thread.java:748) [na:1.8.0_262] Caused by: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'badLogController' for bean class [com.slimsimapps.ava.badlog.BadLogController] conflicts with existing, non-compatible bean definition of same name and class [com.slimsimapps.ava.BadLogController] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:349) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:287) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:132) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:295) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:249) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:206) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:174) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE] ... 26 common frames omitted

Check out http://wikiold.helionet.org/Java_Servlet#Edit_index.jsp_Source The servers are located in Silicon Valley which is US Pacific time. I'm located in US Central time. We have staff in India and Malaysia too. We don't really have a "business time" because all of us are volunteers with real full time jobs, and HelioHost is just a hobby. It's not like we have a HelioHost office where we work 9-5 or anything like that.

Awesome! Check your email. I just finished it.

Unarchived.

Unblocked. It was for failed cpanel logins. If you login at https://www.heliohost.org/login/ that won't happen again.

I'm glad it's working for you now. Marking solved.

Does it work now?

Maybe this will help? https://www.helionet.org/index/topic/41399-hh609325-feedback-and-usage/?p=179952

Unarchived.

Good to know. Yeah, cpanel has a lot more restrictions on passwords. I think they even had a 16 character limit on how long passwords could be at one point. I think they fixed that though.

If you change the webroot you likely need to change your .htaccess too. I would start there. Make sure the paths make sense from the point of view of the new webroot.

PHP may release it on November 26, but then cpanel has to do their thing and release it under the easy apache repo. It usually takes them several months, so I wouldn't expect it anytime soon. You can always get a VPS and install PHP 8 though and solve your high load issues at the same time. For a limited time only you can get 10% off your first 6 months.

Get your load under control and I'll consider it.

Your VPS is done. Check your email.

Unarchived.

Unblocked.

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

The reason mysqlclient is so much faster is because it's written in C and then compiled into an executable. Mysql-connector is 100% python so it is much slower. Here is a link I found that may help. I haven't read through it completely myself so I don't know if they will answer your questions for sure. I did notice it mentions cursors though. https://mysqlclient.readthedocs.io/

Unblocked. It was for failed SFTP logins so make sure you have your credentials saved correctly in your FTP client.

Your account was suspended because Wordpress is causing too much 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. This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress. Something that might help is this simply static Wordpress plugin. It will speed up your site, reduce the load you cause, and reduce your chance of getting hacked. If you try it let us know how it worked out for you. If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

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

From cpanel: We can't provide shell access on our shared hosting because it is too much of a security risk. If you need shell access to run git commands you would have to get a vps https://www.heliohost.org/vps/

You're on Tommy again.