Krydos

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.

I have increased your storage to the maximum, and you don't need to log in to cpanel to keep your account active until 2022-07-16. Let us know if there is anything else we can help you with. Thank you so much for your very generous donation!

Sure, we can do that.

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.

See https://www.helionet.org/index/topic/41398-php-7230-sodium-extension/?p=179955

Does it work now?

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

I'm not seeing any account with the username or domain garytong. If you don't mind posting your email address I can try searching by that.

The bars in the load graph are a measurement of your load compared to everyone else on the server. Consider the following example: Day 1 you get 5000 visitors to your site and the other top 10 accounts on the server get 100 visitors each. Your bars show 100 because you caused the most load, but you don't get suspended because the server as a whole only got 6000 visitors. Day 2 you get 4000 visitors to your site and the other top 10 accounts each get 1000 visitors. Your bars still show 100 because you caused the most load for the day, but today you do get suspended because the server as a whole had 14,000 visitors, which is much more than 6000 total visitors on day 1. It can be kind of confusing to users because on day 2 they actually caused less load than on day 1, but they got suspended when they didn't get suspended on day 1. The way it works is when the server as a whole is overloaded it suspends whichever account is causing the most load to try to keep the thousands of other websites online. So with our system you can actually cause unlimited load as long as the server is still online. Some other hosting providers just suspend you when you use more than some arbitrary amount of memory in a day for example. We don't suspend anyone unless it's absolutely necessary to keep the server online. Hopefully that explains it a little better on how our load system operates. Let us know if you have any other questions.

Yes, the fundraiser is still going on. Just go to https://charity.gofundme.com/o/en/campaign/2020-server-improvements?utm_source=email&utm_medium=news1&utm_campaign=2020gofundme and click donate in the top right. Then type in $30. If you decide to leave a tip it goes to gofundme not us. Then enter your card information and hit submit. The email address that you type in while making the donation gets sent to us in a report as soon as the transaction is processed and we can use that email address to match it up with your HelioHost account automatically. Also you can just let us know you donated by replying to this email. Thanks!

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.

Good news: I verified your 6 month payment, and your last monthly payment went through on 2020-10-03 so 6 months from that date means your VPS is paid for until 2021-05-03. You might want to set a reminder in your calendar to make sure we figure out a payment plan after the 6 months is up. I suspended your monthly payment. I didn't cancel it, and it says I can click reactivate and the monthly subscription should start billing again. We can try that in May and if it doesn't work you can set up a new subscription. I also upgraded your VPS to 2 GB memory for free. Bad news: Your OS upgrade was not successful. Your latest kernel didn't have its initramfs set up correctly, so your VPS won't boot on it's own. If you run the reboot command it won't start back up on its own because the default kernel doesn't work. I was able to get it to boot by selecting the second newest kernel. You should be able to generate a valid initramfs for the newest kernel using these instructions. https://askubuntu.com/a/41939/566733 If you'd like me to fix it for you I can but I'll need root access to do it. You can grant me access by running this command: sudo mkdir -p /root/.ssh/ && sudo echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC2JYn03dd6E+Q2Q2p+UpTV/+Tc9kdrN3AhLL5SKvMt9fV9ZVabMApfT60kJCmWi9U6sjBSx7ohngj0d53i6Cwm6UZqoxl5RJWK1Bky0YEhA2x60bkGUcqm2DMCPkSU2R3PxNcNZN5CDyCEnjrnEUi5BwMcPqvR43tqoVA2kIeUntJfXbI0k5nQ1ewGqnJWmFtJDJjvs7tdJ2f9rQrhGTfXHjuHhFM3ANKu+bIcJkpBd6XH7on1mRiYRnvgLZo0dCXXUQ04cOQYuO1AXIRfou5g/CBJx4eJaRat321Wpmy9EQjsTmCebUSa27oPOmO6KG+8yvHGS4J6jw+awg1iqBTb HelioHost" >> /root/.ssh/authorized_keys That command will allow me to securely log into your VPS as root without your needing to tell me your password.

During the deployment process Johnny renames your .war to append your username to the front. So if you try to deploy a file called test.war it becomes embustil_test.war. This renaming is necessary because there are dozens of other users with java access and if you deployed test.war that means none of those other dozens of people could deploy a file named test.war anymore. However, some .war files are hardcoded to only work with one filename. Obviously the best option is to write your .war files in such a way that they aren't hard coded to only work with one filename, but that isn't always easy. Another option that seems to work for people is to create the .war file with your username already added. This way the file doesn't get renamed on the server because it already has your username and an underscore at the beginning. Let us know if this helps.

Your VPS is done. Check your email.

Unarchived.

Unblocked.