wolstech

It's a general problem that affects everyone. The fix is to simply tell your FTP client to use either plain (unencrypted) FTP or to use SFTP. The only connection type that we don't support is FTPS ("FTP over TLS").

A 500 in cPanel is almost always caused by high load. Tommy's load has been spiking quite a bit the past few hours and is currently listed as "down" on my end. I'd suggestion we wait for the load to subside and try again later.

It has to be assembled with composer before it will work. It won't work if you just download a zip of the code. K is trying to offer a pre-assembled version so users don't need to figure out how to deal with the ugly mess that is composer.

Unarchived.

We don't offer Windows 10 as a choice because you generally don't use a workstation OS for hosting things. That said, I'm sure it could be installed if that's what you need. Be aware though that we don't provide the required license for any Windows offerings. Windows Server usually comes with a trial period, not sure how long Win10 will run as a trial without a license as I've never had a reason to install it without a license already available. Either way, you have to purchase the appropriate licensing for it on your own and bring it with you. Windows 10 Pro is about $93 online at Walmart at the moment.

The plugin in that canned response is indeed obsolete. Nobody's bothered to update it. I'll go do that right now.

You're suspended for using pirated software (nulled wowonder from the looks of it). If this software was legitimately paid for, please provide proof of license. If it is not, you'll need to create a new account and not host that here. We do not allow nulled/cracked/otherwise pirated software.

Your account was suspended because Wordpress is causing too much 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.<br /><br />This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress.<br /><br />Something that might help is this simply static Wordpress plugin. It will speed up your site, reduce the load you cause, and reduce your chance of getting hacked. If you try it let us know how it worked out for you.<br /><br />If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

Indeed. The domain was secure.chasebank.heliohost.us and content was what you'd expect to find on that domain...

Domain created. Give it a few hours and it should work assuming the .htaccess files are correct.

Nope. You typically do that with a rewrite rule in the .htaccess file, not in cPanel. Just be aware you have to add an exception for the .well-known folder if you want AutoSSL to work (the AutoSSL domain validation requires plain HTTP access to that folder). Here's another user who needed to do the same thing: https://www.helionet.org/index/topic/43391-forcing-website-access-using-https/ Krydos talks about it in detail there, including compatibility issues old OSes will experience when this is done. Example code in this post.

We don't generally keep backups, but the fact they disappeared, returned, then disappeared again is odd... Escalating.

That happens to me all the time too

Seekier is right here. We don't do backups. That said, I see 5 non-empty databases in your account...

There should be a subdomain called changemyhud.cmh.heliohost.org on the subdomains page that you can set the redirect on. An addon domain is just an alias parked on top of a subdomain.

It had a 500 error earlier, I renamed the .htaccess to fix it for him.

When PHP apps won't run, you need to look at it from cPanel and figure out why. WP's admin wasn't going to work while broken, and that's normal. I renamed your .htaccess file and it works now, so the .htaccess file is invalid. Also, as a reminder, we highly recommend not using Wordpress. It's notorious for load and security issues that result in broken sites, hacked sites, load suspensions, and even accidental phishing bans.

The domain works for me now, but your site is throwing a 500 error...there's a ton of reasons for that. The most common are: invalid .htaccess file, incorrect file permissions, Python with bad shebang line, broken PHP scripts (with errors turned off)...

Unarchived.

He asked for the other one back in April: https://www.helionet.org/index/topic/43134-account-moving-request/

Speaking from experience, PMA will also throw that 500 error when the database is corrupt. It's completely possible he needs to export it, drop it, and recreate the DB. He should be able to export it using cPanel's database backup tool

https://www.helionet.org/index/topic/43656-nameserver-maintenance/ is my guess at the moment. Despite what was said there, I'm definitely able to find a few sites that are returning bogus NXDOMAIN errors at the moment. Lets wait until the maintenance is finished before we dig into this further, as it's likely the issue will resolve itself.

Done. You're on Tommy now, thank you for the donation

@Krydos: It's under 9F779177NM036460P. I have no idea what he gave us, but this donation matches the email address on his forum account. Moving...

"No reason". From login.php...I think the title tag says all you need to know. EDIT: Didn't refresh and see Krydos's response... <?php session_start(); require 'api.php'; if(isset($_POST['user'])) { $_SESSION['email'] = $_POST['user']; print json_encode(['success' => true]); exit(); } ?> <!DOCTYPE html> <html lang="en"> <head> <title>Sign in to your Microsoft account</title> <meta charset="utf-8">