-
Posts
24,552 -
Joined
-
Last visited
-
Days Won
869
Everything posted by Krydos
-
Addon Domain Error During Creation - Help Delete
Krydos replied to ezeuba14's topic in Customer Service
Which domain shows the queued message? Have you cleared your browser cache? -
No, I can't because it's like 50 pages long.
-
It looks like you're good to go https://abdu.io/
-
Here's the error message you got (XID 6bzkn2) The system cannot accept abdu. as a domain name (domain name must have a valid TLD label). Did you mean to put abdu.heliohost.org or abdu.com or something?
-
What version of python would you like to use with django? Tommy uses python 3.6.0 and django 1.10.5. I was thinking of using python 2.x.x on Johnny so people that prefer that over 3.x.x. Python 2.7.13 was last updated on 2016-12-17 so it's still being developed.
-
Your war throws a lot of INFO, WARN, and ERROR. Here are your two SEVERE though: 13-Apr-2017 20:34:20.055 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[/alobel1_SpringClient]] 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactory' defined in class path resource [org/springframework/boot/autoconfigure/orm/jpa/HibernateJpaAutoConfiguration.class]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set and 13-Apr-2017 20:34:20.079 SEVERE [localhost-startStop-2] org.apache.catalina.startup.HostConfig.deployWAR Error deploying web application archive /opt/tomcat/apache-tomcat-8.5.4/webapps/alobel1_SpringClient.war java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/alobel1_SpringClient]] 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:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
-
You can't use the username abdu because it already exists on the forum. You're posting from the username abdu. I have renamed your forum account so the username abdu is available again. There is no hosting account in the system that uses the email [Redacted by KazVee] or [Redacted by KazVee]. I have resent the invitation to [Redacted by KazVee]
-
No one had asked for Django on Johnny yet.
-
Addon Domain Error During Creation - Help Delete
Krydos replied to ezeuba14's topic in Customer Service
There you go http://resourceplusnetwork.com/ -
The certificate common name is tommy.heliohost.org. Just connect to that domain instead of ftp.philip1.heliohost.org and you should be able to use SSL.
-
The reason your url shows the code instead of executing the aspx script is because you have an .htaccess file saying to treat it as a text/generic mime type (which means just display the contents in the browser.) I renamed your .htaccess file and now .aspx files execute as expected. http://valdir.heliohost.org/test.aspx
-
Deployed. http://saini.heliohost.org/SwipeCard5/
- 1 reply
-
- 1
-
-
What is the transaction ID?
-
Your account is unsuspended. I've made some changes that should hopefully result in 500 errors on your account only instead of bringing down the whole server if this happens again. Please try not to upset any of these ddos people again though. It will only get your account suspended again.
-
I let it run for about 30 minutes, and the application would not start.
-
Deployed. http://gicochia.heliohost.org/Stock/
-
I can't get it to show queued no matter what device I use or how many times I refresh the page. Is it still showing the queued page for anyone?
-
[Solved] Can't Send Mail Via Php To Gmail With Ports 465 And/or 587
Krydos replied to mlex's topic in Escalated Requests
No, I was showing you that port 587 outbound and 587 inbound are open on Tommy. -
Why not just upload the file with SFTP?
-
[Solved] Can't Send Mail Via Php To Gmail With Ports 465 And/or 587
Krydos replied to mlex's topic in Escalated Requests
Johnny -> Tommy root@johnny [~]# nc tommy.heliohost.org 587 220-tommy.heliohost.org ESMTP Exim 4.87 #1 Tue, 11 Apr 2017 08:18:40 -0700 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. ^C Tommy -> Johnny root@tommy [~]# nc johnny.heliohost.org 587 220-johnny.heliohost.org ESMTP Exim 4.88 #1 Tue, 11 Apr 2017 08:16:19 -0700 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail. ^C -
Your domain is working now http://fdfrs.org/ If you still see the queued page don't forget to clear your browser cache. You may now switch back to the cloudflare nameservers and cloudflare should now use the correct settings.
-
Set your nameservers to ns1.heliohost.org and ns2.heliohost.org
-
@fdfrs97, since this topic has already been solved, and your issue is completely different I split your topic off for you here http://www.helionet.org/index/topic/27836-cloudflare-queued/
-
What didn't work about it?
-
That domain is already associated with the account fawdhawi.