Krydos

Actually, your jquery.min.js file isn't jquery at all. It's some random html. http://test.dogily.us.to/images/jquery.min.js You need to download an actual jquery file such as https://code.jquery.com/jquery-3.5.1.min.js

Look at the console when you load that page: jquery.min.js:1 Uncaught SyntaxError: Unexpected token '<' Your jquery file is corrupt. You can probably just edit it and remove that '<'.

What is the url?

Unarchived.

Remote access enabled.

Did you include jquery above this code? The jquery code you're using will only work if you load the jquery library before you try to run the code. The code to load jquery will look something like this: <script type="text/javascript" src="jquery.min.js"></script>

Deleted.

I can install lz4 and tex2img but cython is going to be kind of pointless without shell access. I think you need a vps https://www.heliohost.org/vps/

It can take a few minutes to reactivate an account. If you try to login or change the password while it's inactive still it will fail. I'm glad everything is working for you now.

What is your connection string?

Remote access enabled.

While the majority of our donations through gofundme have come from people in the US, 37 out of 62 have come from countries other than the US so it definitely works wordlwide. Like Byron said we'll take donations of any form though. We just encourage people to try gofundme because we get the lowest fees from them. It varies depending on the size of the donation, but our effective fee rate on gofundme so far is 3.29%. Paypal is about 9% fees on a $5 donation. Bigger donations have a lower fee percentage though.

Alright, your OS has been reinstalled, and is using the same IP and default password as before. Let me know if you need help with anything else.

Which version of python are you using?

High load can cause the login form to reply with Invalid Login even if your username and password are correct when the server is too slow to respond before the login form times out. We're actually working on upgrading our main website right now, and one of the top priorities on the new version of the website is to give a more meaningful error message than just Invalid Login all the time. Johnny is the most susceptible to high load because he is an experimental server and has the most accounts, but high load can affect Ricky and even Tommy occasionally.

You might be confusing GB with GiB. 1 GB is 1000 MB. 1 GiB is 1024 MiB. cPanel measures diskspace in MB not MiB or GiB. You can see a converter here https://www.google.com/search?q=3000+MB+to+GiB This wikipedia page may also be useful and an interesting read for you https://en.wikipedia.org/wiki/Gibibyte EDIT: Here's what it shows for me in WHM

Your account is active and appears to be working fine. Your last login date is today. Your IP address is not blocked. You should be good to go. The supported way to login to your account is at https://www.heliohost.org/login/ Any other login url may not count your last login date and your account could go inactive because you were logging in at an unsupported url.

See https://www.helionet.org/index/topic/41426-donation/?p=180032

I have increased your storage to 3000 MB, and you don't need to log in to cpanel to keep your account active until 2021-01-17. Let us know if there is anything else we can help you with. Thank you so much for your donation!

I have increased your storage to 4000 MB, and you don't need to log in to cpanel to keep your account active until 2021-02-17. Let us know if there is anything else we can help you with. Thank you so much for your donation!

I emailed you about this already, but I'll post here too. Your VPS is still running fine as far as I can tell, and the console responds. My guess is that you blocked ssh logins with the firewall. I can't log in on the console with the default password I sent you though so that probably means you deleted that user, or changed the password. If you want me to disable the firewall for you I'll need to know your current username/password. The other option is I can just reinstall the OS I guess.

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.