wolstech

The domain has been changed. Give it 48 hours. To those who use that script: You must provide the full new domain in the script, like example.heliohost.org, not just example. That was the issue experienced by this user.

Your domain has been changed to edge-gamers.heliohost.org. It may take up to 48 hours to start working. In the future, you can change your domain yourself by using this form: http://www.heliohost.org/home/support/scripts/domain

Something is really weird...I see three separate accounts with different registration dates and IPs, but all with the same username (which shouldn't be possible). In addition, you're only allowed one account. I'm going to escalate this because there should not be 3 accounts with the same username. Once we get that cleared up, we'll need to figure out which account you want to keep since you can only have one, then change your main domain on that account if you still want to change it. @Krydos/Byron: How is this possible? (Search ACTIVE in ACP for a username of "cyber" with no wildcards...3 accounts with same username. Also, 2 appear to be suspended when visited though they're listed as active...)

That script is what you would use, though sometimes it doesn't work. What's your account's username, and the domain you want to use? I can change it for you.

The .tk is the one i see on your account. If you had changed it, it was probably incompletely changed due to a server problem. Since you said the .tk is working, I'll close it for you.

This is completely normal for Johnny. It can take a week to set up accounts because the server is severely overloaded. His perfrmance is equally terrible. If you need something faster and reliable, I would recommend Stevie.

Use a service like this: http://www.setcronjob.com to run as much as you wish. We do not give exceptions for cron because of the extreme load they cause. We limit normal cron and recommend an external service because timing and triggering the job externally makes a cron use less load (the cron daemon uses quite a bit of load when it runs a job, so using a service like that means they handle load from the cron daemon and we just handle the actual program vs. us handling both). You basically sign up on that service, specify the URL to the script (usually it ends up looking something like http://www.example.com/someprogram/admin/includes/cron.php), and give it a schedule. There's some limits on the free version, but if you need some of the stuff offered by the paid version, odds are you'll be suspended for load here anyway.

If you skip moving the DNS to your registrar, you can just use the advanced DNS editor to change the A record for ryanzim.com to the other host's IP. However, if you really want to use different DNS, I think the following should work. First create a subdomain of ryanzim.com in cpanel. This subdomain will become your Heliohost-hosted subdomain. Wait until it's no longer queued and you can see your content/directory listing. Create an A record for the subdomain created above on your new DNS server. Point it to 216.218.192.170 Create an MX record for ryanzim.com on your new DNS server. Point it to the subdomain you created above (you're not supposed to use IPs in MX records, so you can do this to point the MX to Stevie). Optionally create a TXT record for SPF configuration. Create the appropriate A or CNAME record for ryanzim.com on your new DNS server to point it to Github Pages. Point ryanzim.com to the new DNS server at your registrar and allow changes to propagate. Configurations using non-Heliohost DNS are NOT officially supported and have not been tested. As a result, I cannot guarantee that this configuration will work for you. I currently host a single subdomain myself without issue, however I do not have any email services set up on that domain.

This question got left in the dust...do you still need help with this?

This is not supported.

Mysqlnd is enabled on Johnny based on his phpinfo. Johnny runs PHP 5.4, which uses mysqlnd by default. Doesn't appear to be available on Stevie.

Did you drop the table first? If not, drop that table and try again.

Can you post the contents of that file (edit out the password)? Also, be sure your database hostname is 127.0.0.1 (do not use localhost).

I've been wondering about this too. His load has definitely been rather high lately. When I looked earlier, a good chunk of CPU was being used by mysql, crond, and a bunch of PHP processes (all owned by one user). I'm not sure what "normal" looks like on Stevie though. Krydos would know.

The funny thing about php 5.3 and 5.4 is that they are pretty much compatible. I'm not familiar with this program, but if it was possible to get a version that does not require ioncube, it'd probably run on Stevie with minor adjustments. I'm running a php 5.4 app on Stevie myself, I literally changed 2 lines of code and commented out the version check. If Johnny isn't suitable for you and your developer is for some reason unwilling or unable to help you work around Stevie's limitations, you will need to wait for our new server to come online in a few months. It will offer 5.6 (or possibly 7) and the updated components that come with it, as well as the stability of Stevie.

The account strans has been removed. Give it 24 hours to finish cleaning up, then sign up on Johnny. Be aware that Johnny accounts can take up to a week to fully set up due to server load. Also, Johnny account only have ~75-80% uptime. If your Queued page doesn't go away in 24 hours, you just need to wait. If Johnny's unreliability is an issue for you, you might want to see if whoever makes your script for you can send you an older version that can run on Stevie (would need support for ioncube 4.0.9 and PHP 5.3.8). Many developers that have been around for a few years will have an older version that meets Stevie's requirements, since Stevie's configuration was very common in ~2013.

What is your account's username? I'll delete it for you so you can sign up on Johnny. Also, what application are you trying to run? If we knew, we might be able to tell you whether or not it'll even have any chance of running on Johnny before you spend the time trying.

Your domain hasn't finished setup yet (it's still queued). You won't be able to see any files on your site until the account setup completes. For Johnny users, this can take up to a week.

On second thought, this is probably related to what appears to be a damaged MySQL server (again). Everyone else is now reporting similar issues.

You were suspended for 3 cron jobs. The limit is 2 per day. You've been unsuspended.

Stevie's MySQL seems to be crashing frequently. It was down for me a few minutes ago, then was up, and is now down again...this behavior reminds me of the inno failure last year. Escalating.

Down for me too. Stevie's MySQL crashed. Escalating.

The error i see leads me to believe its a damaged database (lost connection during query was an error caused by damaged innodb support last year). Have you tried restoring it from a backup? Also, what is the name of the database? Is the database visible in phpmyadmin? The account itself has nothing wrong with it. Not queued or suspended.

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.

Mobile.uzair.ca should be a proper subdomain with a path of public html, unless the mobile site uses a different installation of Wordpress (in which case point it to the folder containing that installation instead). WordPress itself doesn't like being accessed from multiple domains though, so you should not create a mobile subdomain unless you're showing different content entirely. A responsive theme should adapt itself to the device when visited, and should not require a separate subdomain. CloudFlare can break some responsive themes in certain configurations as well, so if you still use it, it may need to be turned off. Also, just to note: WordPress is extremely prone to being hacked. In fact, hacked WordPress is the leading cause of suspensions for Spam and Phishing here at Heliohost. I would recommend just about any other CMS over WordPress. Using a CNAME will just give you a queued page. Unless you're doing advanced things like pointing subdomains of a domain hosted with us to things that are not hosted here, there should be no reason to edit your DNS manually.