Tony

On Thursday July 29th between 9:00am and 12:00pm PDT we will be upgrading the Phantom server's PHP to the latest version. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to the latest version first then the web servers so for a short time there may be different versions handling command line cron jobs. The reason for this upgrade is to get the latest version of PHP with all the latest fixes. Along with PHP we will also be upgrading the LSAPI version which will bring some performance benefits on the web server side. If you have any questions about this maintenance window do not hesitate to contact support. Date: 07/29/2010 Start time (PDT): 9:00am End time (PDT): 12:00pm Estimated Down Time: None Duration: 3 hour

On Thursday July 29th between 9:00am and 12:00pm CDT we will be upgrading the Mercury server's PHP to the latest version. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to the latest version first then the web servers so for a short time there may be different versions handling command line cron jobs. The reason for this upgrade is to get the latest version of PHP with all the latest fixes. Along with PHP we will also be upgrading the LSAPI version which will bring some performance benefits on the web server side. If you have any questions about this maintenance window do not hesitate to contact support. Date: 07/29/2010 Start time (CDT): 9:00am End time (CDT): 12:00pm Estimated Down Time: None Duration: 3 hour

On Thursday July 29th between 9:00am and 12:00pm CDT we will be upgrading the Mars server's PHP to the latest version. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to the latest version first then the web servers so for a short time there may be different versions handling command line cron jobs. The reason for this upgrade is to get the latest version of PHP with all the latest fixes. Along with PHP we will also be upgrading the LSAPI version which will bring some performance benefits on the web server side. If you have any questions about this maintenance window do not hesitate to contact support. Date: 07/29/2010 Start time (CDT): 9:00am End time (CDT): 12:00pm Estimated Down Time: None Duration: 3 hour

On Thursday July 29th between 9:00am and 12:00pm CDT we will be upgrading the Skyline server's PHP to the latest version. We do not expect any down time during the maintenance window. We will be upgrading the system PHP to the latest version first then the web servers so for a short time there may be different versions handling command line cron jobs. The reason for this upgrade is to get the latest version of PHP with all the latest fixes. Along with PHP we will also be upgrading the LSAPI version which will bring some performance benefits on the web server side. If you have any questions about this maintenance window do not hesitate to contact support. Date: 07/29/2010 Start time (CDT): 9:00am End time (CDT): 12:00pm Estimated Down Time: None Duration: 3 hour

Unlikely to see that variation of the Frog Host CPU tracking as we're looking at better technologies to control CPU. The current system just tracks it we want to be able to pro actively limit users using excessive CPU. So for example we cap all sites at 50% of a single CPU and someone spikes tries to use 100% of one. Their site would still load it would just load slightly slower as they're attempting to use much more CPU than allocated. Cloud Linux is one technology that allows use to do something like that. That example of the 50% is just that an example but it illustrates the idea. Excessive usage would slow down the person doing it rather than using an unfair amount of CPU for an extended period of time.

Funny thing I believe you're a bot. I've seen that picture on several profiles on our forum

Yep with a cPanel backup it should restore everything the same way as it was before. This is assuming the other providers side is generating full backups which is generally the case. I believe it should work fine our system uses the same things others do. So if it's a cPanel one it should still work. We use RBL's just like I imagine every web host does. It's just way to much spam if there isn't filtering going on at the server level. That being said we've whitelisted known IP's before such as twitter. The problem is the IP's may not be known making it difficult to ever really solve the problem. Really they should work on getting themselves off the RBL's. The video files are fine.

I am guessing they actually used a coupon and what they paid is much less. We've brought this up with the developer of the software we use for billing about this bug just has yet to be fixed.

Litespeed is just the web server it has nothing to do with PHP. So whether it's PHP 5.2, 5.3 or 6.0 or whatever it won't make a difference to it. Usually 404 errors are due to mod_rewrite rules so the script has you add them or has it htaccess.txt and wants you to rename it .htaccess. We rarely run into issues with scripts not working and when we do it's usually ones that are extremely old using Apache features not even recommended by them anymore.

You should be able to update the rails version specific to your account. Just need to do it via the Ruby on Rails option in your cPanel.

It is 25% of the first payment the user makes but need to keep in mind almost no one signs up for such a short term. Typical users actually sign up for a year so usually the payout is anywhere from $15-$50. Our affiliate program is not geared towards mass market affiliates so if that's the goal unfortunately we're not the ideal company. We don't do the $60 payout on a $5 hosting account that paid for one month or anything like that. Our other company Frog Host does 50% payout and it's accounts cost much more so payouts are much higher it still is 50% first payment only though.

We'd love to have the systems integrated but there is no decent integration that'll work with our situation. We're hoping that changes when the new version of the support system we use comes out. Right now if we were to do integration it would force users to use the login they have in our billing area. The problem is a lot of people have different emails for billing and support which cause this problem. So we need a system that'll allow logins when you don't have an account and also allow logins when you do. Now as far tickets you can view them without submitting another ticket. https://support.hawkhost.com/index.php?group=default Once you login you can view all the tickets you've ever made.

Nope

Unprofessional? I'm not sure what you expect when you provide a company with fake information and your order then gets rejected and someone from billing asks you why the fake information. You respond and not even 45 minutes later you file a dispute. You were since refunded since your account wasn't even setup. I doubt any company that plans on being around is going to accept an order with fake information. I'm sure fly by night ones will but anyone who plans to be around long term I doubt they'd accept such an order. In the long term it costs a company money as the disputes and fraudulent activity are common when fake information is provided.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.

This has been completed.