Speed Zone Roping

So, This blog is moving to a much faster host !

Not exactly but here is how it is.

I have setup a server that is specialised in WordPress, Joomla, and other very popular PHP scripts

The morale (And what’s new) abou this is the speed, i will tell you about it in a minute

After making a server in over 2 days nonstop work, And after securing it from spammers, hackers, and other annoying people, i modified the WordPress system to use non-trivial software on the server.

Don’t get me wrong, WordPress is one fine software and so is Joomla, but they have been written to work on as many systems as possible, And not tailored to a certain system and it’s resources.

So, i will be selling Lightning Fast WordPress setup, With modified WordPress files to run on the system !

The system is expected to go live in 3 to 5 days, and will offer a free 1 month no credit card requiered trial, For those who opt to buy the service right away, the trial month is added to there account as a free month !

So, to top things off, A live chat person will actually set things up for the clients ! This is not just support, this is a managed blog !

The offering is a 5GB space, on an 8 Xeon Processor server (Two Quad Xeon Processors) with 8GBs of ram serving WordPress, this is nothing like our excellent PLESK offering, this is something you can find nowhere on the internet !

I will keep you updated on how things go as soon as we finish testing the server, Some very uncommon techniques are used to speed up your wordpress blog on this server, And for the same price as all our hosting level1 plans ($2.8/Mo), 5GB space and 100 email mailboxes, and a bunch of other nice stuff

Users on this server will not be restricted in any way, this is simply value added with no compromise for bloggers who want faster blogs (For both admin pannel and blog).

The only restriction to users who have not yet opted to use the server is email limit, this is because spammers usually hit on freee hosting, and we don’t want this server that we have spent so much time setting up blacklisted or sending spam to anyone, This restriction is removed as soon as the user is a paying customer !

So, users were getting

Content Encoding Error (content_encoding_error)

Server response could not be decoded using encoding type returned by server.
This is typically caused by a Web Web site hosting presenting a content encoding header of one type, and then encoding the data differently.

For assistance, contact Customer Support.

And they did

Turned out horde comression for some encodings has issues, Solution was editing C:\Inetpub\vhosts\webmail\horde\config\conf.php, and change $conf['compress_pages'] to false (Turn off compression)

Everything works fine for now, If i intend to host any mail on a Windows server that is.

So, changing the hostname on My CentOS Virtual Machine keeps reverting back to ip-xxx-xxx-xxx-xxx.ip.secureserver.net, Not exactly what i want, especially when there is a 1,000 Emails mail quota for all godaddy VPS, i don’t really use this particular box for anything important, But i do need to have things right on every single box i run, With 10 Servers and 2 Virtual Dedicated servers, i really can use every peice of related information i can use.

So, the PLESK over virtuzzo has a license key, and i very much doubt that it is related to the hostname, but i will keep you posted once i finish the following steps

1- Adding the domain name (Sub domain as domain) to PLESK so that mail routs internally without going to godaddy once things change, So servername.powerdonkey.com domain gets added to PLESK.

Changing in the following places

/etc/hosts

/etc/sysconfig/network

/etc/network/interfaces
Then /etc/init.d/networking restart
/var/qmail/control/me
/etc/httpd/conf/httpd.include
hostname servername.powerdonkey.com
/etc/hostname

/etc/init.d/hostname.sh start

For testing

hostname
hostname -f

In the psa mysql database , in misc table (FullHostName, sso_relay, sso_server, sso_server_user_url), While the first updates from within CP, the other two do not !

Now, what about that… will it requier a full server reboot, or just

/etc/init.d/psa stopall
/etc/init.d/psa stop
/etc/init.d/psa start

The three options for this on a PLESK server running plesk 9.01 and IIS6 is as follows

We will choseto always have everyone in the shared application pool, CPU limit will come after some investigation