wolstech

This is the first time I've ever heard of someone trying to use RAM as file storage. Assuming you're using PHP, it should be automatically saving the files in /tmp if they're received via POST. You should be able to get the name from the $_FILES array. Use move_uploaded_file() to move it into your home folder, or unlink() to delete it. In order to do what you're doing, you have to either being cheating to send the files (i.e. not sending them as files but instead doing something like base64-ing them and shoving them into a normal POST field), or specifically make an effort to do something like using file_get_contents() on the temporary file. By the way, you just got suspended for this yet again. If you don't fix it quickly and it happens again, I'll put a deny from all in your .htaccess file so you can stay unsuspended with your site offline until you can rewrite this badly written file uploader.

Did you add the domain in cPanel under aliases?

Krydos is the only one who really knows anything about node...let's see if he knows.

I wish we could ban WP. It's complete garbage... We'd lose half of our users if we did though...and we need all the users we can get, because ads don't pay if nobody sees them.

That address is mine. You're probably seeing it from when I was helping you with your domains (I log in as the user through WHM and create the subdomains so I can park the extra domains you need).

The easiest fix for Wordpress...is to not use Wordpress. Errors like this are very common with WP because the software is very inefficient and poorly written. Installing extensions makes it even worse. Literally any other CMS will run better on our servers than WP. If you really insist on using WP, start by removing all of your plugins. Wordfence and Woocommerce are two that are infamous for causing extreme load (that leads to 500 errors if your lucky, suspensions if you're not). Add them back one at a time until the issue returns, then do away with the defective one. Odds are you have one or two in the list causing this problem.

You have to do it yourself in cpanel. There's an option under Software for Java. Note that since your account is new, you likely haven't requested Java. You have to do that first and wait for it to be activated. Since you're on Johnny, the estimated wait is currently 4 months before you can deploy it. (In contrast, Tommy users have a wait of about 1 day, so you might want consider moving to tommy instead).

Eu.org isn't fully compatible with our service any longer due to nonstandard changes on their end. Specifically, their domains will always fail the name server checks even when correctly configured. If you use one of their domains, it must be your main domain, and users can only have one.

You can do this in cpanel in the dns zone editor.

Much better. Thanks

There's definitely something wrong with that server. I cannot get into WHM or cPanel from numerous IP addresses (all "Connection Refused"). We've also gotten several email support requests for login failures and cPanel being down, so it's not me.

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.

Your password didn't change. The server you're on (Ricky) is just experiencing problems with cpanel at the moment. You'll be able to log in once this is fixed.

Cpanel is down on that server yes. Your site seems to be working properly, but you won't be able to log into cpanel until it is fixed.

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?

Unfortunately we can't change your password to that because you just posted it on a public forum. Our support email is not private and password should never be sent through it. As for changing the password, the password cannot be changed because Ricky is down at the moment.

Unblocked.

Unblocked.

That account is on Johnny, not Ricky. Try logging in here: https://johnny.heliohost.org:2083/ (use your username hikmal, not your email address, when logging into the server directly)

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).