Title: Internal Server Error
Last modified: August 31, 2016

---

# Internal Server Error

 *  Resolved [mdnnnn](https://wordpress.org/support/users/mdnnnn/)
 * (@mdnnnn)
 * [10 years ago](https://wordpress.org/support/topic/internal-server-error-416/)
 * Hello,
 * i’ve been using plugin for few days and it worked fine until yesterday.
    When
   i try to translate some words and save i get error message: Internal Server Error
   Any idea what is causing this?
 * [https://wordpress.org/plugins/loco-translate/](https://wordpress.org/plugins/loco-translate/)

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

 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378242)
 * There have been many reports of internal server errors which I’ve never been 
   able to reproduce, let alone attribute to any part of my plugin. Often these 
   seem to be down to security software that blocks Loco’s behaviour, but I’ve been
   unable to verify that.
 * Please try version 2.0 beta version: [https://localise.biz/help/wordpress/translate-plugin/developers](https://localise.biz/help/wordpress/translate-plugin/developers)
 * If the problem persists in v2, please start a new topic. I’m closing this as 
   support for v1 has ended.
 *  [pablosekkei](https://wordpress.org/support/users/pablosekkei/)
 * (@pablosekkei)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378247)
 * Hi,
    I have the equal problem: [Thu Aug 11 12:01:15 2016] [error] [client xxxxxxxxxxxx]
   Premature end of script headers: admin.php, referer: [http://xxxxxxxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s](http://xxxxxxxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s)
 * I try the version 2.0 beta an also produces the equal mistake.
    Any solution?
 * Thanks
 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378248)
 * > I try the version 2.0 beta an also produces the equal mistake.
 * I need to be able to reproduce this error, so please outline exactly how I can
   see it happening.
 *  [pablosekkei](https://wordpress.org/support/users/pablosekkei/)
 * (@pablosekkei)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378249)
 * Hi,
    I go to [http://xxxxx/wp-admin/admin.php?page=loco-translate](http://xxxxx/wp-admin/admin.php?page=loco-translate)
   and Internal server error appear
 * [http://prntscr.com/c4cqrw](http://prntscr.com/c4cqrw)
 * My memory_limit is 256M. The Logs show me this ->
 * [Thu Aug 11 12:57:24 2016] [error] [client xxxxxxxx] Premature end of script 
   headers: admin.php, referer: [http://xxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s](http://xxxxxxx/wp-admin/plugins.php?plugin_status=all&paged=1&s)
 * BR
 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378250)
 * That is a link to version 1 of the plugin. You said you are using version 2.
 * I’m guessing you clicked the return link from the plugin activation page, but
   the links in the new version have changed. I guess this is going to be an issue
   for others when switching over, so I’ll add in some kind of redirect.
 * However, the screen that WordPress should give in this situation should not give
   you a 500 error unless something else is wrong.
 *  [pablosekkei](https://wordpress.org/support/users/pablosekkei/)
 * (@pablosekkei)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378251)
 * Hi Tim
 * yes I made a mistaki upload de version. I put the 2.0 and works Fine
 * Thanks for your time!
 *  Plugin Author [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * (@timwhitlock)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378252)
 * no problem. I’ve added a legacy link redirect into v2 now anyway, hitting `page
   =loco-translate` will redirect to `page=loco`. Serves me right for changing the
   page slug, but I got tired of it being so long.

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

The topic ‘Internal Server Error’ is closed to new replies.

 * ![](https://ps.w.org/loco-translate/assets/icon-256x256.png?rev=1000676)
 * [Loco Translate](https://wordpress.org/plugins/loco-translate/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/loco-translate/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/loco-translate/)
 * [Active Topics](https://wordpress.org/support/plugin/loco-translate/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/loco-translate/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/loco-translate/reviews/)

 * 7 replies
 * 3 participants
 * Last reply from: [Tim W](https://wordpress.org/support/users/timwhitlock/)
 * Last activity: [9 years, 10 months ago](https://wordpress.org/support/topic/internal-server-error-416/#post-7378252)
 * Status: resolved