Tony

We will be updating the Mercury server kernel to the latest version on Thursday April 30th at 10:30am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/30/2009 Start time (EST): 10:30am End time (EST): 11:00am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Mars server kernel to the latest version on Thursday April 30th at 10:00am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/30/2009 Start time (EST): 10:00am End time (EST): 10:30am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Skyline server kernel to the latest version on Wednesday April 29th at 10:30am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/29/2009 Start time (EST): 10:30am End time (EST): 11:00am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Saturn server kernel to the latest version on Wednesday April 29th at 10:00am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/29/2009 Start time (EST): 10:00am End time (EST): 10:30am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Neptune server kernel to the latest version on Tuesday April 28th at 11:00am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/28/2009 Start time (EST): 11:00am End time (EST): 11:30am Duration: 30 minutes Estimated Down Time: 10 minutes

We will be updating the Jupiter server kernel to the latest version on Tuesday April 28th at 10:30am EST. We estimate this will result in about 10 minutes of down time while the server reboots. Keeping kernels up to data is a necessary step in order to stay on top of performance improvements as well as have the latest security fixes. Date: 04/28/2009 Start time (EST): 10:30am End time (EST): 11:00am Duration: 30 minutes Estimated Down Time: 10 minutes

All VPS's should be back up including any of the VPS's that did not start back up automatically. Sorry about any inconvenience this may have caused and lets hope for another 160+ day uptime on the machine or longer.

VM's are still starting up. Should be another 15-20 minutes to have all of them up. It's just a last few which are a little slower starting up.

At around 10:40PM EST on April 18th our Raptor VPS node kernel paniced. This meant that the entire system became inaccessible requiring a reboot of the system. After the reboot the system was able to start back up with no issue and is currently restoring services. The process of restarting every VM will take some time we're keeping a close eye on this to make sure all of them start back up. This affected not only the node but our web site as well which runs on this node currently. We'll continue to update this post about the progress of starting back up all VM's.

awstats are already activated on all servers. If you have a new account you need to allow up to 24 hours for a stats run before it shows up.

Highly more likely you got blocked by the firewall system for repeated login failures. The pluto machine I don't even think has gone over a load of 1 since we deployed it. This on a 8 CPU machine that could handle a load of 8 and continue to serve pages fine. I really don't understand why any problem ever people say ooh the server is overloaded. That never seems to ever be the case. A person posts a link to a PHP script with a syntax error and tells us it's because we overload our servers O_o. I guess all the brainwashing by the "non oversellers" results in this sort of thing.

There are quite a few other ways to do it: RewriteEngine on RewriteRule !.(js|ico|gif|jpg|png|css)$ index.php [/CODE] Just sends it all to index.php except for js,ico,gif,jpg,png and css. Then you also have [CODE] [COLOR=#000000]RewriteEngine On RewriteCond %{REQUEST_FILENAME} -s [OR] RewriteCond %{REQUEST_FILENAME} -l [OR] RewriteCond %{REQUEST_FILENAME} -d RewriteRule ^.*$ - [NC,L] RewriteRule ^.*$ index.php [NC,L][/COLOR] For any file it finds.

I'm not quite sure I understand the question. But assuming it's a site and you're talking about the public_html folder that cannot be changed. The docroot of a domain will always be the public_html folder. You can create an bootstrap index.php file in it and have the controllers, config ect. ect. below it though.

Glad I could help.

You're completly incorrect the base url is just nothing. /home/username/public_html is where your site starts serving files. So if you upload a file there is goes to http://sitename.com/ . It does not go to http://sitename.com/home/username/public_html/ So say you upload two files index.html and page.html to your public_html folder and wanted to link from index.html to page.html your href would just be page.html. It would not have any extra paths or anything like that

I imagine the software you're using when they say base url they're talking about it as the url of the site. So you'd want just / or blank or whatever it is to make so it's nothing. Then you just upload your files to the public_html folder as you have.

The problem would be your reseller account has it's own rvskin package system and you do not have the subversion option enabled. Login to WHM then on the menu near the bottom there is a Rvskin option. From there you should be able to setup a default package setup with subversion enabled.

Yep you're correct it is done through where you registered your domain.

That would mean it has not propagated. Did you make sure to change your name servers to the ones mention in the account information email?

Propagation is dependent on your ISP and so the only real way to know is based off of the IP that your site is showing for you or the content that is displayed (something you uploaded). As for uploading you can start uploading files the second you have access to cPanel you do not need to wait for DNS propagation.

2) I'm not really sure about this as the idea is to tell you which one you're currently on. I think the better solution may be to change the highlight of the active one. So rather than some sort of underline the image is a different color completely. Going to need to think about this one.

We've worked with the OP to resolve the issue. Turns out we were a bit wrong about the cause being their themes themselves. It turns out their phpthumb installations were all allowing hotlinking which some malicious users have found out. As a result their account was serving thumbnails for we don't even know how many images. So a lesson to everyone out there if you have phpthumb make sure you configure it via the config file to not allow hotlinking.

You made 2 tickets received responses within 20 minutes on both. You also made a third ticket received a response within minutes. Your account was disabled because you did not act on a warning we gave you about your usage. You did not properly create html in your wordpress themes you've been distributing as a result now your account is serving all the images for people using these themes as well as generating all the thumbnails for these themes. So you've created yourself a mess and it's become worse and worse as your themes become more popular. We warned the account owner asked them to resolve it and get back to us and they told us they don't even own the account. Whomever was actually running the account never contacted us in any way so we disabled the account. We cannot just let this continue to get worse as no one was willing to fix the problem or at least tell us they're trying to.

No clue at this point have yet to make a decent graphic. The ideal would be to have the litespeed box there but it's not transparent As for the globe that's actually Cody doing multi variant testing on our main page you can read about it at: http://www.hawkhost.com/blog/2009/03/22/multivariate-testing/ As for other changes they're already in our svn waiting for other changes to be completed before they're pushed out to the live site.

You usually can find coupons on our specials page http://www.hawkhost.com/Specials