Title: SiteGround Setup
Last modified: October 7, 2016

---

# SiteGround Setup

 *  Resolved [ntarantino](https://wordpress.org/support/users/ntarantino/)
 * (@ntarantino)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/siteground-setup/)
 * Hello, I just moved over to SiteGround and was setting up WordFence. I began 
   setting everything up and had to add the php.ini file and manually added the 
   auto_prepend_file file it gave me. Once I did that and pressed continue everything
   seemed to work correctly.
 * This is my screenshot: [https://postimg.org/image/at4r1co1n/](https://postimg.org/image/at4r1co1n/)
 * I have waited around 30 minutes and nothing changed.
 * I then went to this : [https://docs.wordfence.com/en/Web_Application_Firewall_Setup?utm_source=plugin&utm_medium=pluginUI&utm_campaign=docsIcon](https://docs.wordfence.com/en/Web_Application_Firewall_Setup?utm_source=plugin&utm_medium=pluginUI&utm_campaign=docsIcon)
 * I followed the steps here where it says: If php.ini has been edited manually 
   but the changes still do not take effect and when the php.info file comes up 
   I can confirm that the uto_prepend_file is setup correctly.
 * I went online with SiteGround support to confirm that the setup with Apache +
   suPHP was correct and they confirmed.
 * So now I needed to come here to ask what I might be missing 🙂

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

 *  [wfalaa](https://wordpress.org/support/users/wfalaa/)
 * (@wfalaa)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/siteground-setup/#post-8276583)
 * Hi ntarantino,
    Did you follow these steps specifically for “[SiteGround and other hosts without .user.ini support](https://docs.wordfence.com/en/Web_Application_Firewall_Setup#SiteGround_and_other_hosts_without_.user.ini_support)“?
 * Also, you may need to confirm with SiteGround support that you are editing the
   correct php.ini file.
 * Let me know how it goes,
    Thanks.
 *  Thread Starter [ntarantino](https://wordpress.org/support/users/ntarantino/)
 * (@ntarantino)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/siteground-setup/#post-8279967)
 * I finally solved it by reading slowly and following those steps 🙂
 * Working great! Glad to get this up and running. I felt like I had a site being
   attacked and so instead of learning for a week I put it in protection mode right
   away. What’s the difference by leaving learning mode for a week and just going
   into it right away?
 * Thank you!
 *  [wfalaa](https://wordpress.org/support/users/wfalaa/)
 * (@wfalaa)
 * [9 years, 7 months ago](https://wordpress.org/support/topic/siteground-setup/#post-8283927)
 * Glad to hear that!
    Setting the “[Firewall Status](https://docs.wordfence.com/en/WAF#Firewall_Status)”
   to “Learning Mode” for a couple of days or even a week should help in preventing
   the firewall from blocking some of your plugins/themes requests by mistake (false
   positive), check “[How to use Learning Mode](https://docs.wordfence.com/en/Web_Application_Firewall_-_How_to_use_Learning_Mode)”
   for further details.
 * Thanks.
    -  This reply was modified 9 years, 7 months ago by [wfalaa](https://wordpress.org/support/users/wfalaa/).

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

The topic ‘SiteGround Setup’ 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/)

 * 3 replies
 * 2 participants
 * Last reply from: [wfalaa](https://wordpress.org/support/users/wfalaa/)
 * Last activity: [9 years, 7 months ago](https://wordpress.org/support/topic/siteground-setup/#post-8283927)
 * Status: resolved