wolstech

As you're aware, the server is Pacific time. I live in Eastern Time as well. Just subtract 3 hours when setting it. To set for once a day, enter an hour and minute, and put * in the day/weekday/month fields. Note that crons are on a 24 hour clock too. I have a 4:18EDT cron, which is scheduled as 13 hours 18 minutes (1:18PM PT), with * in the other fields. Also, I recommend not running crons on the hour or half/quarter hour since the servers tend to run a lot of them at those times. Schedule it for a random minute like 3:07 if you can.

Down the road its possible we might support it, but there are AFAIK no plans to support this at this time, even if cpanel is upgraded.

What is your username and domain?

You were suspended for running 3 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.

That account is not suspended. I see a blank white page which is being served by whatever you put on your account. If you still see the suspended page, please clear your cache.

Because our version of cPanel does not support SSL with a Shared IP Address. It's not because we don't want to support it, it's because the software we run can't handle it at this time.

We only charge you for it because our provider charges us for it. We just pass our cost of the dedicated IP address to you. We cannot afford to give away free dedicated IP addresses. SSL is the only service that we offer that is not free Since you cannot pay for the IP address, you cannot use SSL.

That's Johnny's shared IP. That is not a dedicated IP address. If you made the payment, please post the paypal transaction number and your heliohost username so the IP can be set up. It doesn't happen automatically.

No limit on visitors per day. We also do not monitor bandwidth usage. What we DO monitor is CPU and RAM usage, and accounts that use too many resources will get suspended for high load. Normal websites shouldn't run into these limits (it's usually stuff like proxies that cause such suspensions). If you send a lot of emails you can get suspended as well (we limit email to about 50/day), but this is less common unless you have issues like forum spammers or malware.

OK. I'll close this for you. If you want to delete your account, you can do so here: http://www.heliohost.../scripts/delete

Did you purchase a dedicated IP address first? We require a dedicated IP address to use SSL functions.

I don't know how the script that detects this works, but its safe to assume it's "In a 24 hour period." It can be 1 job that runs twice, two that each run once, etc. But no more than two things should run in a 24 hour period.

You cannot log in or reset your password because your account was suspended for running too many cron jobs. The limit is 2 executions per day, you had 3. I've unsuspended you, try logging in with your original password.

Krydos will be able to specify the best port to use. I'm not sure if our firewall even distinguishes TCP from UDP packets since I don't know much about its configuration. Escalating.

It's blocked intentionally and we generally frown upon opening them. Our recommendation is that you change your game server's port to one that's already open. Would it be possible to host the game server on a port like 443, 2082, or 2096 instead?

The HTAccess has nothing to do with this issue. You have Cloudflare which is still serving stale DNS. Cloudflare is pointing your domain to Stevie's shared IP address (216.218.192.170), which is no longer associated with your account. Stevie doesn't know what to do with requests for misc314.com on its shared IP since your account is on a dedicated address. Either get CF to refresh it's DNS from our nameservers so CF uses your new dedicated IP (there may be an option to do this, if you used manual A records instead of NS records, you'll need to edit them), or change your domain's nameservers to ns1.heliohost.org and ns2.heliohost.org to eliminate cloudflare and have our servers handle your domain directly. After you do this, wait 24 hours and clear your cache.

Our system doesn't list when you were suspended. We did have the suspension system on Stevie suspend a few too many accounts the other day due to load, so it's very possible you were caught in that issue. Since you've never had this issue before, I wouldn't worry about it too much unless you changed something recently or it happens again.

Moving to customer service.

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.

It was for high load. You've been unsuspended. Several others have experienced strange high load suspension today (Byron was even suspended for this...), so it's likely it was nothing on your end that caused it. If it happens again, let us know and we'll see what's causing your load. By the way, you're the oldest active account here at heliohost. 8 years and counting, created June 30, 2007 That's some dedication to our service.

We fixed Johnny a few weeks ago. The plan is to eventually apply this fix to Stevie as well. I'd suggest free analytic sites like statcounter until we implement it, since we don't have an estimated time for the fix. I'm waiting on it too for an app of mine. I'll escalate this to have the databases removed for you.

Are you in Stevie? Softaculous is broken on Stevie (related to the broken MySQL server...). These should install fine on Johnny. Also, what is your username and domain?

You can't drop these yourself. An admin needs to drop them for you. What are the database names?

Pretty much. Backward compat is one of our bigger motivations, stability being the other. And yeah, PHP development is something where you're better off targeting old versions. I actually have a custom PHP app that I recently back ported from PHP 5.3.8 to PHP 5.2.x after someone wanted to use it on an even older server. :-/

No chance on 5.6. The most you'll be seeing in the near future will be 5.4 on Stevie. At some point in the future we probably will get 5.5 on Johnny. The deprecation of mysql() functions is one of the big roadblocks, as a LARGE number of users on our servers are using software that relies on these and other deprecated functions. These programs will generate deprecation notices or other errors when updated. The 5.4 update broke sites on Johnny...and coming from 5.3.23 it was quite minor in contrast to 5.5 and 5.6.