wolstech

PHP isn't (and never has been) installed per account...it's installed once per machine, but run under the user accounts via suPHP. If we ever get a new server I could see us offering something like this. Until then, don't count on it.

Your domain's DNS has something wrong with it. Escalating. @Krydos: NS2 seems to have this domain record, but NS1 gives NXDOMAIN.

My understanding is that that function requires significant resources we don't have, not to mention more complexity. With that said, I can't see us supporting that feature even if we update cpanel...things are already overloaded and don't work half the time.

Krydos might be able to tell you what file. I'll escalate it for you.

You're welcome Glad to hear its working for you now.

Can you see if this exists? /home/ashrafjp/backup-1.22.2016_08-46-43_ashrafjp.tar.gz If so, download it and manually transfer it. As for the FTP failure, the last line suggests a software issue: That's not good. This feature is likely just never used, so nobody has run into this before that I'm aware of. Perhaps Krydos knows more about this. Escalating...

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.

You're likely stuck in the firewall. An admin can check and unblock you if needed.

That account is active (though its domain hasn't finished setting up yet). Would you like me to email a new password to the email address you registered with?

Change your cPanel password here: http://stevie.heliohost.org:2082/frontend/x3/passwd/ Be sure to select "Synchronize MySQL Password" when changing it. After that, log out and in again and it should work.

What's the name of the database?

Your password has been reset. Please check your email.

It's not the account layout, its the name of the domain that's embedded in the certificate that matters. A wildcard certificate to include all subdomains will have "*.example.com" on it. A normal certificate will only have "example.com" on it (without the *.). What the docs refer to is a third option: multiple domain certificates. These are certificates good for a specified list of multiple (sub)domain names (these are sometimes called "SAN Certificates" because the SAN field on the certificate is used to include the alternate (sub)domain names). If you use a such a certificate, you need to reissue and reinstall your certificate with the new domain included if you decide to add a new secure subdomain later on. We only support one certificate per physical person (an account can only have certificate per IP, only 1 IP per account, and you cannot have two accounts). The only way to cover example.com as well as subdomains is to use either a multiple domain certificate (as described above and in LE's docs) or a wildcard certificate (if LE decides to support it...they don't right now).

Your password has been reset and a new password has been emailed to the address on file for the account maicol07.

You can't change your password because your account is suspended for inactivity. Please renew it first: http://heliohost.org/home/support/scripts/renew

This support request is being escalated to our root admin.

We don't offer that, but if I'm understanding your goal right, there's ways to accomplish what you're doing. The web root for addon domains can be changed/set when you add the domain. The root cannot be changed for the main domain. Very often, people set up addon domains with their web root as /home/username/public_html/domain.tld/ Be aware though that a domain set this way would not be able to access /home/username/public_html/someotherfolder/, as to it, nothing above the domain.tld folder exists. I think you can make an FTP account that uses such a folder as its root too, so you never see the stuff in the home/username/ folder or in the base public_html folder as long as you use that FTP account. A 301 redirect would be fine to redirect a folder to the root. Also, CNAME records cannot he used to shorten a URL, only to point a domain/subdomain to another domain (which, if hosted here, will actually cause the domain with the CNAME to show a permanent queued page).

500 errors when using cpanel are normal due to the process limit. Accounts are limite in how many processes they can run, and cpanel opens a lot of them when you log in. As a result, apache can't open php to run your site, and spits out that error.

IP address is yearly according to Krydos (who pretty much runs the place). I'd have to ask though, as our website tells a different story. As for Lets Encrypt, I don't know if we support it as I haven't personally read the detailed documentation for their service. If it uploads something over FTP, you're probably good. If it uses SSH, it's not supported. Also, I think browsers will still see security warnings in its current state (it hasn't gotten the cross-certificates it needed last I heard).

Yes you must get a dedicated IP address. That's what the $12 fee is for. Our provider charges us $12 for it, so we just pass the cost to you. As for the certificate, yes, that must be obtained from a certificate authority. We do not sell certificates. Many are $10-50 a year depending on vendor for regular ones. Wildcard ones are extremely expensive (on the order of $200-500 a year).There are some promising upcoming free providers though. Let's Encrypt is probably the biggest of them (now a public beta), but I'm not sure if they ever got the stuff required to prevent browsers from showing warnings, and you need to use a linux PC with it installed to generate them.

@omni, I split your post into a new topic: http://www.helionet.org/index/topic/22977-domain-already-exists-in-apache-configuration/

Yep, fixed itself yesterday morning sometime.

That hasn't worked in years. There are no plans to fix it since we don't really use reputation anyway.

Disabling features is one way to do it. Features like user tracking, logging, and similar can be resource intensive, so disable those. Automatic emailing and other background features should also be turned off (email especially, since you can get suspended for sending too many emails as well as for resource usage). I'm not familiar with PPBoard, but from what I can see, it does seem to have a lot of functionality. Perhaps try different software if disabling features doesn't help. You can also move to Johnny where you have more resources. Just be aware that the uptime is terrible at less than 75%...

It depends upon what kind of certificate you use. You need what's known as a "wildcard certificate" (a certificate for *.example.com) if you want it to cover subdomains. A regular certificate (for just example.com without the *. ) will not cover them. Be aware that such certificates are extremely expensive compared to regular ones. If you need SSL cheaply, your best bet is to either: Not use subdomains Create a secure.example.com subdomain and buy a certificate just for secure.example.com to secure that subdomain. Everything will be unencrypted except for that one subdomain. Use the secure subdomain to store things like payment scripts and login systems and leave the rest of your site unsecured. Also, if you do SSL, use Stevie. Johnny's performance is already terrible without it, and the SSL will just that poor performance even worse.