Title: Secure WordPress Breaks Site!
Last modified: August 20, 2016

---

# Secure WordPress Breaks Site!

 *  Resolved [tpaine54](https://wordpress.org/support/users/tpaine54/)
 * (@tpaine54)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/)
 * There needs to be a third option to augment broken/works called “Broke my site!”.
   Amateur hour.
 * Warning: require(inc/swWSD.php) [function.require]: failed to open stream: No
   such file or directory in /home/content/88/7797788/html/wp-content/plugins/secure-
   wordpress/secure-wordpress.php on line 112
 * Fatal error: require() [function.require]: Failed opening required ‘inc/swWSD.
   php’ (include_path=’.:/usr/local/php5/lib/php’) in /home/content/88/7797788/html/
   wp-content/plugins/secure-wordpress/secure-wordpress.php on line 112

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/breaks-site/page/2/?output_format=md) 
[→](https://wordpress.org/support/topic/breaks-site/page/2/?output_format=md)

 *  [Tevya](https://wordpress.org/support/users/thefiddler/)
 * (@thefiddler)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198641)
 * Yep, upgrading killed my site too! DO NOT UPDATE!
 *  [Tevya](https://wordpress.org/support/users/thefiddler/)
 * (@thefiddler)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198645)
 * download 2.0.1 here to fix your site: [http://wordpress.org/extend/plugins/secure-wordpress/download/](http://wordpress.org/extend/plugins/secure-wordpress/download/)
 *  [alanpae](https://wordpress.org/support/users/alanpae/)
 * (@alanpae)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198653)
 * I got the exact same error message about line 112. Removed the whole directory
   tree and will downgrade to 2.01.
 * DO NOT UPGRADE!
 * alan
 *  [windracer](https://wordpress.org/support/users/windracer/)
 * (@windracer)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198802)
 * Took me a while to figure out it was this plugin that killed my site. Thank goodness
   downgrading worked. Ouch.
 *  [cito](https://wordpress.org/support/users/cito/)
 * (@cito)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198804)
 * Same happened to me, I updated to new version of Secure WordPress plugin and 
   it broke my site, not only would the admin panel no longer load the entire site
   would no longer load.
 * Was able to fix by ssh’ing to my site and going to wp-content/plugin folder and
   manually deleting via rm -r secure-wordpress directory.
 * then the site was back up with no problems.
 * Hopefully the creator will update their plugin or post a reason why it’s breaking
   sites all of the sudden.
 *  [gshag33](https://wordpress.org/support/users/gshag33/)
 * (@gshag33)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198840)
 * Same thing happened to me..
 * Luckily did a Google search and found this thread
 * Deleted SecureWP plug-in directory over FTP and site is working again
 *  [zicocarioca](https://wordpress.org/support/users/zicocarioca/)
 * (@zicocarioca)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198843)
 * Another victim here.
 * > Warning: require_once(inc/json.php) [function.require-once]: failed to open
   > stream: No such file or directory in /home/content/86/7318986/html/wp-content/
   > plugins/secure-wordpress/secure-wordpress.php **on line 105**
   > Fatal error: require_once() [function.require]: Failed opening required ‘inc/
   > json.php’ (include_path=’.:/usr/local/php5/lib/php:/home/content/86/7318986/
   > html/wp-content/plugins/instapress/instagram-php-api/:/home/content/86/7318986/
   > html/wp-content/plugins/instapress/classes/:/home/content/86/7318986/html/wp-
   > content/plugins/instapress/PowerHour_Geocoder/’) in /home/content/86/7318986/
   > html/wp-content/plugins/secure-wordpress/secure-wordpress.php on line 105
 * **DO NOT UPDATE.**
    If you did, delete the plug-in directory via FTP. Then cross
   your fingers, like you do every time you upgrade anything. Science, pff.
 *  [soullotus](https://wordpress.org/support/users/soullotus/)
 * (@soullotus)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198866)
 * I updated 3 plug-ins..can’t remember what they were, and I got the same thing.
   I am not all that savvy. Since I can’t get onto my website, how do I fix this?
   
   I don’t know what FTP is.
 *  [Gal Baras](https://wordpress.org/support/users/galbaras/)
 * (@galbaras)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198868)
 * Just updated to 2.0.2 and got a missing JSON file message. Went back to 2.0.0
   and it works.
 *  [soullotus](https://wordpress.org/support/users/soullotus/)
 * (@soullotus)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198871)
 * If anyone else here is clueless like I am, I just called my hosting company, 
   and they helped me fix this. When all else fails…good luck everyone.
 *  [paulzag](https://wordpress.org/support/users/paulzag/)
 * (@paulzag)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198873)
 * If you don’t know what FTP is you probably should **NOT** be automatically updating
   plugins.
 * Your site will be fine. I think the developer accidentally left the sub-directories
   out of the package.
 * Go vote BROKEN on the plugin directory so WordPress will hopefully remove the
   update here [http://wordpress.org/extend/plugins/secure-wordpress/download/](http://wordpress.org/extend/plugins/secure-wordpress/download/)
 * As others have said just delete the plugin directory. If you don’t know how to
   use SSH or FTP then do this:
 * Log into the control panel of your site (normally cpanel or cp) use the file 
   manager to navigate to wp-content/plugins/
 * delete the secure-wordpress directory.
 * install v2.0.1 from [http://downloads.wordpress.org/plugin/secure-wordpress.2.0.1.zip](http://downloads.wordpress.org/plugin/secure-wordpress.2.0.1.zip)
 *  [rbmark](https://wordpress.org/support/users/rbmark/)
 * (@rbmark)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198876)
 * Me too! I get a fatal error on line 112.
 *  [microberto](https://wordpress.org/support/users/microberto/)
 * (@microberto)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198878)
 * LOL. Way to test. Breaks for me on WP 3.1.x
 *  [zepolo](https://wordpress.org/support/users/zepolo/)
 * (@zepolo)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198881)
 * Yep, upgrading killed my site too
 * Remove this plugin !
 *  [archproject](https://wordpress.org/support/users/archproject/)
 * (@archproject)
 * [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/#post-2198885)
 * Same here …. damn … got panic for a while and just deleted it via FTP and site
   works again. What the heck happened

Viewing 15 replies - 1 through 15 (of 22 total)

1 [2](https://wordpress.org/support/topic/breaks-site/page/2/?output_format=md) 
[→](https://wordpress.org/support/topic/breaks-site/page/2/?output_format=md)

The topic ‘Secure WordPress Breaks Site!’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/secure-wordpress.svg)
 * [Acunetix Secure WordPress](https://wordpress.org/plugins/secure-wordpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/secure-wordpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/secure-wordpress/)
 * [Active Topics](https://wordpress.org/support/plugin/secure-wordpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/secure-wordpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/secure-wordpress/reviews/)

 * 22 replies
 * 20 participants
 * Last reply from: [WebsiteDefender](https://wordpress.org/support/users/websitedefender/)
 * Last activity: [14 years, 9 months ago](https://wordpress.org/support/topic/breaks-site/page/2/#post-2198898)
 * Status: resolved