wolstech

The domain http://real-islam.eu.org/ has been manually configured with a document root of ~/public_html/real-islam.eu.org/ on your account. It should start working shortly, and SSL should work within 24 hours. The arab doctors domain was already set as your main domain so no configuration was necessary.

That's the normal configuration. Keep in mind that those settings only work for your main account's username. If you create additional FTP users, you need to use the settings I posted earlier for those extra accounts.

I have to manually install SSL for users. PM me the certificate and I'll install it.

Sometime in the past 3 months, eu.org changed their requirements to follow a non-standard practice only used by one other registrar in the world. Because of this non-standard requirement, eu.org cannot be used as an addon domain or as an alias. It must be used as your main domain. You can change your main domain here: http://heliohost.org/classic/support/scripts/domain

Are you using the right connection type? Created FTP accounts require these settings to work: Host: johnny.heliohost.org Port: 21 Encryption: None / Plain FTP

Krydos never checks his PMs unless told to do so. Neither do I...

Solid reds across the board for him: http://heliohost.grd.net.pl/monitor/ Server does seem to be alive, but certain things on it aren't working. cPanel seems to be dead, but Apache is alive, as is SSH and FTP. Any ideas?

Unblocked.

Unblocked.

Change your name servers to NS1.heliohost.org and NS2.heliohost.org and it'll work. Alternately, add a CNAME record named "static" with a value of "techpill.live" on CF's website in the DNS zone for techpill.live. Please keep in mind that some functionality like FTP and mail will not function for that subdomain unless you remove CF entirely. I doubt that's an issue for a static asset domain... (Please keep in mind that HelioHost does not support CF, and many of the functions in cPanel do not work as expected when CF is configured for a domain. We recommend against users using CF unless they have a good reason to do so).

What domain is it?

You can get load averages programmatically from the server if that's what you mean. Simply make a script that reads /proc/loadavg (e.g. file_get_contents then run it though explode to get an array with averages in it), then do as you please with the numbers. You can even make your scripts react to the load if you want so they stop doing heavy things when it's up. Being an average, it isn't real-time, but it's pretty close, especially the 1min number.

Considering this domain now points to 000 and they've also already banned him, I'm going to assume it is indeed for phishing.

Yep. Load again...please try to fix it quickly. Things running in a tight or infinite loop are a common source of this, so depending on how your code is written, it's completely possible that caused it. Unsuspended.

The common internet ports are open outbound: 21,25,80,443,8080, as well as cpanel ports (2082 and 2083). Others are by request only with good reason given. We need the port and the IP of the remote server you'll be connecting to. We do not allow custom daemons, so inbound ports cannot be opened.

The account was automatically suspended because we have reason to believe it was intended to be used for phishing or other illegal activity. Can you explain why your domain is extremely close to that of a large bank?

cPanel does not support changing the main domain's document root. It must always point to public_html.

Unsuspended.

It was suspended for having too many SFTP connections open. I've never seen that in my career here. Please try to limit the number of connections you open at once to something reasonable (less than 5 is probably good). Most clients have a setting for number of concurrent connections you can adjust to control this. Unsuspended.

As flaze said, check the trash if you used the file manager. If you used something like ftp though, it's just gone. We don't keep backups of active user accounts, so we have no way to un-delete files.

Max execution time is too low most likely...

Did it sit there for 30 seconds then fail? If so, the execution time is probably too low to run it. Krydos might have some additional ideas about this.

Mine did that on Lily as well...it got to 90% on mine, spit out an error, but was successful after refreshing. I think that one is actually a bug. It's kind of an ironic error because a code of 0 in most PC programs is "success". That error is basically readable as "Error: Success". Check the file dates and times. I believe March 9 is the date my files had after the update. The system works fine.

Unblocked. Failed SFTP logins...make sure you use only your cpanel username and password to log into SFTP. If you create additional FTP accounts, they need to use plain FTP on port 21.

That account is working, but the software installed on it is not. Please clear your cache to get rid of the queued page. The privacy warning is normal since Johnny accounts don't come with SSL certificates (Ricky and Tommy include SSL certificates). You can install a certificate from a source like ZeroSSL (and wait a few hours for it to take effect once you do), or just not use SSL. The 500 error is due to broken software on your end that you'll need to fix or remove. The most common cause of a 500 error is permissions (make sure files are 644, they tend to upload as 664 if you use SFTP), or invalid .htaccess files.