Krydos

Your site is password protected so I'm not sure if asp.net is installed on your account or not.

Of course.

I haven't been able to find one. Sitepad was the cheapest/best option I found. That's why we did a trial of it. Running a joomla site doesn't require any coding knowledge. You can try it out by installing it through the softaculous button in your cpanel. I'm not sure what kind of website you need exactly, but HelioHost actually used joomla for our main website from 2008 or so until 2017 or so. We never got hacked a single time either which is pretty good for a cms. Whatever you do stay away from wordpress though.

Cpanel is in control of everything. Without cpanel we wouldn't even have http access.

Cpanel and SAML are not compatible. So if you can get all of your pages created in one month then you can let it expire and your pages should all still work.

Sitepad is $5 per month https://sitepad.com/pricing How many months do you want to use it for? I believe you can keep the website pages after the subscription ends. You just have to edit the code if you want to make a change.

We tried it out eleven months ago https://www.helionet.org/index/topic/29740-site-builder/ As far as I know, you're the first person to ask about it. While the trial was active maybe a dozen people tried it out, and for the most part they didn't think it was worth it. If it was a free product it would make sense to use it, but doesn't make sense to pay for a product that is only used by one person every eleven months. If you want to make a donation specifically for sitepad I'll install it for you.

03-Aug-2018 14:29:22.158 SEVERE [localhost-startStop-2] org.apache.catalina.startup.ContextConfig.beforeStart Exception fixing docBase for context [/tssinfo_savemytime] java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:225) at java.util.zip.ZipFile.<init>(ZipFile.java:155) at java.util.jar.JarFile.<init>(JarFile.java:166) at java.util.jar.JarFile.<init>(JarFile.java:103) at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:93) at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:69) at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:99) at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:122) at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:89) at org.apache.catalina.startup.ExpandWar.expand(ExpandWar.java:130) at org.apache.catalina.startup.ContextConfig.fixDocBase(ContextConfig.java:615) at org.apache.catalina.startup.ContextConfig.beforeStart(ContextConfig.java:748) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:301) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:395) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) That means it's an invalid zip file, and has been corrupted somehow. Try renaming it from .war to .zip on your home computer to see if you can unzip it.

You should be able to download your backup from https://www.heliohost.org/backup/ Let us know if you have any problems.

Try changing your password.

No, because the tomcat log files have potentially sensitive information pertaining to all of the accounts with java enabled and showing them to you would violate our privacy policy. You can either ask for something specific related to your account, or better yet write your servlet to make its own log files in your home directory.

@wolstech, I changed his domain for him. It was lightsoft2.heliohost.org and lightsoft.heliohost.org was on his old suspended account. @nacer, ssl should start working again within 24 hours when autossl runs.

It's not a permanent change. As soon as the ddos ends we're going to move back to the original ip. As should be the case with all good service monitors, we have no control over that site. The person who runs it is very busy, and I don't want to bother him about it only to make him change it back in a couple days or whatever.

The reason why your account is suspended is because your database has been hacked. Whatever data it contained is already deleted/corrupted and it probably contains illegal content. You'll need to use whatever the latest backup you downloaded prior to the hack.

You can see your mining results at https://www.heliohost.org/heliomine/scoreboard/

It's working now https://www.sslshopper.com/ssl-checker.html#hostname=industryus.ca

New email address provided via Facebook, and an invitation to create a new account has been sent.

What is your username or main domain?

There you go https://secege.heliohost.org/secege_hs/

See https://www.helionet.org/index/topic/33698-can-i-use-my-maildomainca-domain-for-email-when-i-havent-resolved-the-blacklist/?p=151229

Looks like you need to get removed from the google blacklist before AutoSSL will work. You can try https://wiki.helionet.org/Installing_a_Let%27s_Encrypt_SSL_Certificate but it might give the same error.

There you go https://krydos1.heliohost.org/56/phpinfo.php

Neither of those will work. If your website was up you could access your cgi script by going to lustboy.heliohost.org/cgi-bin/gettingUsers.py in browser or with a cron command such as /usr/bin/python3.6 /home/lustboy/public_html/cgi-bin/gettingUsers.py

Sometimes cloudflare causes more problems than it solves. Cloudflare only operates on port 80 and 443, so it makes sense that 2078 would have appeared closed.

The problem is the ddos attack. We're trying various methods of mitigation to see what is the most effective. The best solution to the problem is switching to Ricky or Tommy which aren't affected by the ddos attack.