Title: Update caused error message
Last modified: August 22, 2016

---

# Update caused error message

 *  Resolved [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/)
 * Hi I just updated BPS from 50.8 to 50.9 and the message for the whole site including
   the any admin panel page is now:
 * “Briefly unavailable for scheduled maintenance. Check back in a minute.”
 * Not sure what to do here!
 * [https://wordpress.org/plugins/bulletproof-security/](https://wordpress.org/plugins/bulletproof-security/)

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

 *  Thread Starter [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351029)
 * The website has returned to normal, because wordpress automatically deleted the
   plugin after a failed update.
 * So I went to install the newer version and it’s says it’s still there, though
   not showing on the plugins page, but still the files are in the ftp.
 * Should I delete it from the FTP and then download again?
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351060)
 * > “Briefly unavailable for scheduled maintenance. Check back in a minute.”
 * This is a standard WordPress message that is displayed when upgrading WordPress
   itself (and maybe plugins now too). The maintenance message is displayed by using
   the .maintenance htaccess file that is added by WordPress to your website root
   folder during upgrades and then it is normally automatically deleted after the
   upgrade is finished/completed.
    [https://wordpress.org/support/topic/get-rid-of-briefly-unavailable-for-scheduled-maintenance-check-back-in-a-minute?replies=2](https://wordpress.org/support/topic/get-rid-of-briefly-unavailable-for-scheduled-maintenance-check-back-in-a-minute?replies=2)
 * If for some reason your site/server has intermittent connectivity problems or
   the server hiccups during an upgrade then the .maintenance htaccess file may 
   still be in your website root folder and you would need to manually delete it.
   The bigger more important issue to look at would be the server connectivity issue/
   problem or “out of memory” issue/problem.
 * Yes, when WordPress displays a message that the “Destination folder already exists.”
   then you would use FTP or your web host control panel file manager and delete
   the /bulletproof-security/ plugin folder (or if this happened while upgrading
   another plugin then you would delete that plugin’s folder).
 * Once again the bigger more important issue/problem sounds like a server connectivity
   problem or “out of memory” problem. ie the server is losing connectivity intermittently
   or is out of memory. You should check your server logs and also contact your 
   web host about this. It could be that something on the server is starting to 
   fail, such as a hard drive or something else that needs to be looked at or repaired.
 * Or another more likely possibility is that you have a plugin installed that is
   using up all of your PHP server’s memory and resources so you should look into
   that as well. Your Server logs will have an error like “out of memory….” and 
   show which plugin is using up all the PHP server memory.
 * FYI – I see that you have Wordfence installed from your thread history and Wordfence
   has the common known problem of using up all your PHP server’s memory and resources.
 *  Thread Starter [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351104)
 * I’ll contact the hosting provider.
 * In the meantime to reinstall the plugin, should I use the ftp to make the htaccess
   file the default one again?
 * Thanks for the help
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351108)
 * Nope, you would keep the secure htaccess file. The problem is not related to 
   BPS and is either one of the 2 things I mentioned above – most likely it is an
   out of memory problem caused by Wordfence, which is a very common.
 * Deactivate Wordfence first. Then use FTP, delete the old /wp-content/plugins/
   bulletproof-security/ plugin folder and install the BPS plugin again using the
   WordPress Plugins >>> Add New plugin installer. By doing these steps you will
   keep all of your BPS database settings and will only be installing new BPS plugin
   files.
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351116)
 * And speaking of memory you should have a PHP memory_limit directive setting of
   at least 128M. Once you get BPS reinstalled go to the BPS System Info page and
   post your PHP Actual Configuration Memory Limit. If you try to use Wordfence 
   with anything less than 128M you are going to have lots of out of memory problems.
   😉
 *  Thread Starter [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351136)
 * Ok thanks again, BPS is re-installed and working well again! Spoke to my hosting
   provider too and they said they found some ‘node’ issues and got them fixed. 
   That was the only issue they could find. This is what it says in the php system
   info:
 * PHP Version: 5.3.24
    PHP Memory Usage: 4.3 MB WordPress Admin Memory Limit: 256M
   WordPress Base Memory Limit: 40M PHP Actual Configuration Memory Limit: The Memory
   Limit value is not available from your Server.
 * With wordfence activated:
 * PHP Version: 5.3.24
    PHP Memory Usage: 4.82 MB WordPress Admin Memory Limit: 
   256M WordPress Base Memory Limit: 40M PHP Actual Configuration Memory Limit: 
   The Memory Limit value is not available from your Server.
 * Thoughts?
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351140)
 * “The Memory Limit value is not available from your Server.” Means that nothing
   is being returned by your server for this check:
 *     ```
       get_cfg_var('memory_limit');
       ```
   
 * You can check your memory limit by creating a php file, adding this one line 
   of code below in that file and uploading it to your website root folder. If you
   named the file example.php then you would use this URL to view your PHP server
   info: your-domain.com/example.php
 *     ```
       <?php phpinfo(); ?>
       ```
   
 * If your memory limit is not at least 128M then contact your host to have them
   increase your memory limit to at least 128M.
 *  Thread Starter [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351149)
 * The memory limit is 64M so I’ll get them to increase it!
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351156)
 * Yep, the clues were pointing to a low memory limit setting being the most likely
   cause of the root problem. I think you will be very pleasantly surprised after
   the memory limit is increased to 128M. Overall site performance will be much 
   better and you should not run into anymore problems when installing things. One
   last thing. Whatever you do – DO NOT use the Live Traffic feature in Wordfence–
   that feature will kill your website’s performance and use up all of your website’s
   memory. 😉
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351163)
 * Delete the php file that you created and uploaded to your website after you are
   done with it. It is not a huge security risk to leave that file, but no point
   in making it easy for hackers to find clues about your PHP server.
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351289)
 * Is the issue/problem resolved? Can this thread be resolved? If so, please resolve
   this thread. If not, please post any additional information.
 * Thread Start Date: 10-1-2014 to 10-2-2014
    Current Date: 10-6-2014
 *  Thread Starter [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * (@maliwoot)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351293)
 * Resolved:
 * Updated memory to 128M – Problem with updating BPS fixed.
 * If it is returned to 64M – Updating BPS results in wordpress displaying a maintenance
   mode or a ‘no data recieved page’ and an unexpected removal of the BPS plugin.

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

The topic ‘Update caused error message’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

 * 12 replies
 * 2 participants
 * Last reply from: [maliwoot](https://wordpress.org/support/users/maliwoot/)
 * Last activity: [11 years, 8 months ago](https://wordpress.org/support/topic/update-caused-error-message/#post-5351293)
 * Status: resolved