Title: Server changes
Last modified: July 7, 2020

---

# Server changes

 *  Resolved [sirrahikkala](https://wordpress.org/support/users/sirrahikkala/)
 * (@sirrahikkala)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/server-changes-2/)
 * Hey, is there something I need to do when our sites changed IP and server from
   Apache to Litespeed? I have a gut feeling that at least firewall is using way
   too much cpu on new hosting.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [sirrahikkala](https://wordpress.org/support/users/sirrahikkala/)
 * (@sirrahikkala)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/server-changes-2/#post-13093887)
 * Up
 *  [ramwf](https://wordpress.org/support/users/ramwf/)
 * (@ramwf)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/server-changes-2/#post-13107176)
 * Hi sirrahikkala,
 * After migrating from Apache to Litespeed, you may need to remove the Firewall
   Extended Protection and re-optimize it. As a general rule we’ve tested the Web
   Application Firewall and it should use minimal resources. Let us know if you 
   run into any issues or errors.
 * Thanks,
    Ram

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Server changes’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [ramwf](https://wordpress.org/support/users/ramwf/)
 * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/server-changes-2/#post-13107176)
 * Status: resolved