Title: htaccess Causing 500 error
Last modified: August 21, 2016

---

# htaccess Causing 500 error

 *  [Trueimagedesigns](https://wordpress.org/support/users/trueimagedesigns/)
 * (@trueimagedesigns)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/htaccess-causing-500-error-1/)
 * Hello,
    My website is continually being downed on a fairly regular basis (~4-
   5 times a week) by a corrupted htaccess file. This causes it to display a 500
   internal server error. Whenever it happens i just replace the htaccess file with
   the original and it works fine (short term fix).
 * The htaccess file seems to get randomly jumbled up a little differently each 
   time it happens. Some times it will simply add an extra ‘>’ and sometimes it 
   will duplicate random chunks of code.
 * Seen this issue discussed but no resolutions posted. please let me know what 
   we can do. I am running Easy Restaurant Menu Manager – Extended.
    Hope to hear
   back from you. Thanks
 * [https://wordpress.org/plugins/easy-restaurant-menu-manager/](https://wordpress.org/plugins/easy-restaurant-menu-manager/)

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

 *  Plugin Contributor [Richard Royal](https://wordpress.org/support/users/richardroyal/)
 * (@richardroyal)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/htaccess-causing-500-error-1/#post-4693699)
 * I’ve seen this issue a few times across different plugins and themes.
 * I’m not really sure what is causing it because I’ve never been able to reproduce
   it on dev. This plugin has no reference to that file so it’s probably some weird
   hosting thing
 * The easiest solution is to change the file permissions on the htaccess file. 
   Removing write permissions makes sense from a security standpoint as well. Try
   644.
 *  [t2design](https://wordpress.org/support/users/t2design/)
 * (@t2design)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/htaccess-causing-500-error-1/#post-4693956)
 * I’ve had this problem too. I keep getting the letter “s” being added to the last
   line of the htaccess file causing the site to crash. I can’t seem to find a solution
   other than to change the file permissions. My theme developer said it’s not them(
   Modernize – Goodlayers), my dedicated virtual host (MediaTemple) says it’s not
   them, and so far all the plugin authors say the same. I’ve tried re installing
   WP, but the problem persists. Let me know Trueimage if you figure it out and 
   I will do the same!
 *  Plugin Contributor [Richard Royal](https://wordpress.org/support/users/richardroyal/)
 * (@richardroyal)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/htaccess-causing-500-error-1/#post-4693959)
 * We are not able to reproduce this issue and are still recommending that the server
   not have write access to the htaccess file. Can you tell me a little more about
   your hosting platform?
 * OS
    PHP Version

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

The topic ‘htaccess Causing 500 error’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/easy-restaurant-menu-manager_fbf8f8.
   svg)
 * [Easy Restaurant Menu Manager](https://wordpress.org/plugins/easy-restaurant-menu-manager/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/easy-restaurant-menu-manager/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/easy-restaurant-menu-manager/)
 * [Active Topics](https://wordpress.org/support/plugin/easy-restaurant-menu-manager/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/easy-restaurant-menu-manager/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/easy-restaurant-menu-manager/reviews/)

## Tags

 * [500 error](https://wordpress.org/support/topic-tag/500-error/)
 * [htaccess](https://wordpress.org/support/topic-tag/htaccess/)

 * 3 replies
 * 3 participants
 * Last reply from: [Richard Royal](https://wordpress.org/support/users/richardroyal/)
 * Last activity: [12 years, 2 months ago](https://wordpress.org/support/topic/htaccess-causing-500-error-1/#post-4693959)
 * Status: not resolved