wolstech

We've known about this. It's been around for a while. In fact, we have a Wiki article on it: http://wiki.helionet.org/Installing_a_Let%27s_Encrypt_SSL_Certificate Also, if you use Tommy, that server has AutoSSL. It hands out free DV (domain verification) SSL certificates from Comodo to every domain on the server, and renews them automatically as they expire.

You have to request it and wait again. You can do so using the Java option under Software in cpanel.

You need to delete your account and sign up again unless you wish to donate. Since the account has not yet been created, do you want me to cancel your pending creation so you can try again tomorrow?

This is a known issue. Johnny's PHP broke last night, likely due to that maintenance we were performing (which involved rebuilding PHP and Apache). Please watch https://www.helionet.org/index/topic/29106-johnny-php-does-not-work/ for updates.

Unblocked.

The account saber is listed as active.

PHP is broken on Johnny. https://www.helionet.org/index/topic/29106-johnny-php-does-not-work/

AutoSSL is already supported on Tommy and is already disabled on Johnny (the testing server). It takes up to 24 hours for a certificate to issue after adding a domain though.

You found the answer already, but I just wanted to add that the minimum donation is $1 for those who find this topic.

Johnny php is currently broken. You can follow this forum post for updates: https://www.helionet.org/index/topic/29106-johnny-php-does-not-work/

This is a known issue. PHP is currently not working on Johnny. Please follow this forum topic for more information and updates on a fix: https://www.helionet.org/index/topic/29106-johnny-php-does-not-work/

No estimate on a fix. The root admin has to look at it. He usually checks in a few times per day, so watch that forum post I linked earlier. He'll probably respond there when he has more information on this issue.

PHP is broken on Johnny. Others are having the same problem. You can watch for a response in this forum topic: https://www.helionet.org/index/topic/29106-homepage-problem/

Duplicate of https://www.helionet.org/index/topic/29106-homepage-problem/

This support request is being escalated to our root admin.

Johnny php appears to be messed up, likely from the maintenance. My site on Johnny does the same thing. Not sure if that maintenance finished or not yet... Escalating.

First off, do you have/can you prove you have a license for IPB? (We don't allow nulled software.) As for your concerns... Pcntl_exec is a security risk based on what I've read since it's basically just exec() that reuses process space. This one does need to go since exec is already disabled. We intentionally enabled the display_errors because we get too many complaints about 500 errors with them off. I and many others prefer them on, and 90% of other hosts also have them on by default. People expect the errors to appear if their script is broken. A regular 500 error doesn't tell you anything useful. Escalating to disable pcntl_exec()...

That's not our suspended page. Our suspended page looks like http://tommy.heliohost.org/cgi-sys/suspendedpage.cgi Also, that domain works properly for me. It's a DNS issue with your computer, network, or your ISP.

It's archived. Escalating so it can be restored.

You need to put the stuff that's inside the "Web Files" folder in the prometheus folder. You put the entire "Web Files" folder in http://tldgc17.heliohost.org/prometheus/, when you were only supposed to put the contents in there. You need to move everything in public_html/prometheus/Web Files/ into public_html/prometheus/, then delete the (empty) Web Files folder. As for the 500 error, there's a ton of things that can cause that. Invalid .htaccess files are the most common cause.

Unblocked.

We don't give WHM access to users, its for root admins only. Ioncube is not supported on Johnny. You need a Tommy account for it. Also, do you have a license for WHMCS? We don't allow nulled (pirated) software.

He had us set that to run every 5 minutes, so likely a combination of frequent, repeated runs and poorly written code. I would suggest reducing its run frequency and looking into optimizing that code.

Gone.

There's an option for it in cpanel. It's at the top under "directory privacy". Be aware that if you use this, too many failed logins from a single IP in a short time will get the network that PC resides on an IP ban, and you'll need to ask us to unblock you.