Krydos

Did this work for you, pieviks?

Unsuspended. Fix it quickly.

21-Jul-2019 20:16:00.912 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.core.ContainerBase.addChildInternal ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/luqman_backend]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:743) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:703) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1858) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:772) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:426) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1629) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:304) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1176) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1398) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1402) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1370) at java.lang.Thread.run(Thread.java:748) Caused by: org.springframework.jmx.export.UnableToRegisterMBeanException: Unable to register MBean [HikariDataSource (HikariPool-3)] with key 'dataSource'; nested exception is javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:625) at org.springframework.jmx.export.MBeanExporter.lambda$registerBeans$2(MBeanExporter.java:551) at java.util.HashMap.forEach(HashMap.java:1289) at org.springframework.jmx.export.MBeanExporter.registerBeans(MBeanExporter.java:551) at org.springframework.jmx.export.MBeanExporter.afterSingletonsInstantiated(MBeanExporter.java:434) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:862) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549) at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140) at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:742) at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:389) at org.springframework.boot.SpringApplication.run(SpringApplication.java:311) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.run(SpringBootServletInitializer.java:151) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.createRootApplicationContext(SpringBootServletInitializer.java:131) at org.springframework.boot.web.servlet.support.SpringBootServletInitializer.onStartup(SpringBootServletInitializer.java:91) at org.springframework.web.SpringServletContainerInitializer.onStartup(SpringServletContainerInitializer.java:171) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5098) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 19 more Caused by: javax.management.InstanceAlreadyExistsException: com.zaxxer.hikari:name=dataSource,type=HikariDataSource at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) at org.springframework.jmx.support.MBeanRegistrationSupport.doRegister(MBeanRegistrationSupport.java:137) at org.springframework.jmx.export.MBeanExporter.registerBeanInstance(MBeanExporter.java:671) at org.springframework.jmx.export.MBeanExporter.registerBeanNameOrInstance(MBeanExporter.java:615) ... 36 more

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

By not filling /tmp? If you have any scripts that write or read from /tmp you need to edit them and have them write and read from /home/neverfor/tmp instead. That way your scripts will only crash your account rather than crashing all the other thousands of accounts on your server.

Remote access enabled.

You can find the exim logs in /var/log/exim4/

Closing due to inactivity.

I'm assuming you want the user ereyes_entipisa to have access to the database ereyes_entipi, and the user ereyes_sigesp to have access to the database ereyes_siges?

I installed the files for you. You need to create the mysql database for it and then you can finish the installation.

Please change your nameservers to ns1.heliohost.org and ns2.heliohost.org.

You already have reverse DNS set up. Just google "reverse dns lookup" and type in your IP address, or run the command dig +noall +answer -x 216.218.228.90

The heliohost2.gmail.com in the SOA record is actually an email address, not a subdomain. Ashoat got tired of all of the account creation emails being sent to his personal account so I set up that junk mail box because cpanel requires some admin email address. Any domain that uses Heliohost DNS will have that same SOA record.

Done. You should now be able to log in and your website should start working within 2 hours.

Does it work using http (instead of https)?

Your donation has been verified and your storage increased to 3000 MB. Thanks again.

The certficate covers www now too. https://www.sslshopper.com/ssl-checker.html#hostname=stockdiv.com All you had to do was uncheck the ssl box, click save, check the ssl box, and click save and it generates a new certificate and installs it for you. The only reason you were having issues doing this yourself before is because you used htaccess to block lets encrypt's access to your well-known/acme-challenge directory.

There you go https://nonsense.win/phpinfo.php

Done. You should now be able to log in and your website should start working within 2 hours.

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. 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...

Please post the following information: Your cPanel username Your main domain The server that you are on

Bots trying to brute force their way into your server using random email addresses is very common. You had http to your .well-known directory blocked with .htaccess so new ssl certificates couldn't be installed. I edited your https redirect and added an exception for the .well-known directory. This allowed me to issue a new lets encrypt certificate that covered mail.stockdiv.com in addition to stockdiv.com. Then I edited the exim configuration to use the new ssl certificate and restarted exim. This tester looks happy now https://www.checktls.com/TestReceiver

You could use a tool like https://philiplb.de/sqldumpsplitter3/ or you could just upload the .sql file to /home/roguitar/filename.sql and ask one of the admins to import it for you.

Fixed. Thanks for noticing it.

Closing due to inactivity.