Guys. So far everything rocks with litespeed. Using it production-wise. Just have some minor glitches, like the mod_rewrite for wordpress issue (separate thread), and not getting the webmail at port 80. Basically, with interworx, webmail is at port 2443, the default for their internal webserver I think. However, with apache, I think it's being proxied (mod_proxy as per interworx reply) to be accessible at port 80, like http://domain.com/webmail. This is done automatically and no webmail folder really exists per website. However, with the switch to litespeed, webmail is no longer accessible at port 80, and now our clients have to go through port 2443, which everyone of my clients hate. Anyway I can get litespeed to work the same way? Any suggestions? Below is the response I got form interworx support, hoping that helps as well Here are my questions to them and their reply, hopefully some can chime in.... 1. webmail is no longer accessible from domain.com/webmail. Now I have to put the port 2443 to access webmail. Before with apache, webmail was in port 80 at domain.com/webmail The apache configuration for webmail at port 80 is in the /etc/httpd/conf.d/iworx.conf. It uses apache's mod_proxy, so my best guess is that litespeed doesn't handle that apache configuration? Perhaps the litespeed folks could provide an alternative. 2. webserver part of nodeworx is empty. I mean the RRD graphs now looks like no traffic at all.... This is because that particular graph is generated from the mod_watch apache module, which litespeed doesn't support. There's not much we can do about this one unfortunately.