Jak naprawiono błąd 500 Internal Server Error w WordPress?

676 komentarzyZostaw odpowiedź

1. Ivan

   Also, how to create an .ini file on a mac???

   Odpowiedz

2. Ivan

   What if it’s NOT the .htaccess file? Can we then change the filename back .htaccess??

   What if it’s NOT the plugins? Can we simply change the plugins folder name back to what it was??

   These are details we should know about.

   Thanks!

   Odpowiedz

   • WPBeginner Support

     Yes, if it was not due to plugins folder or .htaccess, then you can put them back as they were.

     Odpowiedz

     Administrator

3. gks

   thanks this was so helpful.

   Odpowiedz

4. philip

   Thankyou so much, I had installed a plugin which had somehow corrupted the .htaccess file, renamed it to .htacces_old as per the advice on this page, and all’s back working again, if you cant find the .htaccess file on your server, it could be hidden, cpanel has an option to look for hidden files.

   thanks guys

   Odpowiedz

5. Akinshola Samuel

   When all the files in your „wp-content” are empty, you always get the server (both locally and remotely). Took me longer time before recognising this.

   I was moving the an existing wordpress engine alognside many other things, Unfortunately the wp-contents and it’s respective folders were all empty.

   Finally, Happy when I solve this.

   Odpowiedz

6. Max B

   Thank you guys for saving my day! This solved the issue for me, thank you!

   Odpowiedz

7. Sofia Berglund

   Thanks! Great tutorial. Turned out for me that, when I was unactivated the plugins, I got another error-message saying i had some corrupt @media print-code in the functions.php. Took that away and got my page back

   Odpowiedz

8. Donald

   Make sure index.php has permissions of 644. Somehow mine has 777 when transferred from one server to another.

   Odpowiedz

   • John

     DONALD !!! you’re a life saver … thanks to the WP beginner platform also

     Odpowiedz

9. Lewis James-Odwin

   Great Video, solved my problem in 54 seconds! (.htaccess issue)

   Odpowiedz

10. Keek

    I must have spent 4 hours trying everything I found online. In the end, turns out I was running an old version of PHP. When I updated it in my cPanel, the 500 error was gone.

    Odpowiedz

11. krishna

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, webmaster@ and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    how to solve this error?

    Odpowiedz

12. M Jones

    My problem was actually a corrupt wp theme rather than a corrupt plugin.

    To solve I renamed the corrupt theme (Oxygen) (which gave me a white screen) than named Twenty Sixteen „oxygen” so that my site would use Twenty Sixteen (a working theme) as my theme. Than I switched using dashboard to Twenty Fourteen (my second favorite installed theme) than again used my file editor to rename Twenty Sixteen back to „twentysixteen” & Oxygen to „oxygen.corrupt”.

    I think my theme did not download properly, making it corrupt.

    Thanks for pointing me in the right direction!

    Odpowiedz

13. Alia

    Thank you so much you saved me a lot of time!

    Odpowiedz

14. mayur

    Thank you so much for so complet information!

    i have a .htaccess problem.. solved.. now working as charm..

    Odpowiedz

15. SHYOPAT

    Someone pointed me to your article (thank heavens) I did the htaccess file change and it helped it for two minutes. Then I did the php memory thing and that helped for a few minutes as well, then back to the internal server error. I’m currently working on trying to figure out if it’s a plugin. If that doesn’t help… then I’ll do the core files. And then after that… I have no idea. I guess I’ll try my hosting provider again.

    Odpowiedz

16. Den

    I always check .htaccess file first…

    Odpowiedz

17. Will Paro

    Is it possible to have an Internal Server Error only on select computers, but not others?
    That is the issue I’m dealing with right now.
    I have 6 sites all hosted through one account via GoDaddy. All are showing an Internal Server Error. They were fine this morning, but now nothing.
    Problem is that GoDaddy says that they see the sites just fine.
    I can pull the site up in gtmetrix.com and analyze it with no issues.
    Please help.
    Every computer I use PC, Macs and Chromebooks all show internal server errors, but gtmetrix.com and GoDaddy says everything is fine.

    One of the sites is

    Thanks in advance

    Odpowiedz

18. Jesu

    You save my life!!

    Thanks a lot from Spain!

    Odpowiedz

19. antony agnel

    Phew…thanks a lot guys!

    A new guy here…installed 'bulletproof security’ plugin on my wordpress site & got an Error 500!

    Was shit scared…& finally found out about your site and this article – finally fixed it by applying your tip to rename to .htaccess file to .htaccess_old!

    Once again, thank you so much – you guys rock!!

    Odpowiedz

20. hendra

    Hi Guys

    I have a questions in regards of 500 internal server error, i experienced the problem with a plugins [JSON API] when i type example.com/api/ – it is showing 500 internal server error.

    any advises on how to solve this problem? much appreciated before.

    Odpowiedz

21. Linda

    Thank you!
    In my case, it was the theme that was broken (my fault for tinkering around), not a plugin. I renamed the theme folder .mytheme-deactivate like in your plugin example, and hallelujah, I could access my site again! (I simply activated a different theme, but I could probably uninstall and re-install the original theme if I wanted to)

    Odpowiedz

22. Aviroop Chowdhury

    Disabling solved my issue. Thanks.

    Odpowiedz

23. Mike

    Sometimes this is a bug in your own PHP code.

    For this it’s best to use a binary chop 'echo’ method. That is add a simple echo 'fred1′; exit; into your code starting at the top of the index.php. If you see 'fred1′ displayed when you visit your site then you know it’s a PHP bug and not any of the other reasons. (Note I used a .htaccess online validator to check the syntax of my .htaccess file too, in order to rule that out).

    Once 'fred1′ is displayed now move it halfway down the index.php file (useful to increment the integer each time too, e.g. fred2, fred3 etc). If the server error occurs then you know you need to move the statement up. If fred1 etc is printed then you need to move it further down the code. If you get to an include or require statement then you then delve into that file in the same way.

    I found the offending PHP file in under 10 minutes. You should then use php -l whateverfile.php to find offending line in that file and also to know what the syntax error is. If 'php -l’ doesn’t give you the syntax error then you should read this:

    The 'php -l’ would need to be done by remote logging into your hosting account. If you can’t do this then as this article says, contacting your hosting support can be useful to find the php log file.

    Odpowiedz

24. Darrin

    You’re a life-saver! Renaming my plugins directory worked. Thank you!

    Odpowiedz

25. Peter Ishola

    I have tried all the options given in this article but it’s still the same. the error message appears on both the admin and the web pages of my site. I’d appreciate more options to solve this problem. The error message is:

    500 – Internal server error.
    There is a problem with the resource you are looking for, and it cannot be displayed.

    Thanks

    Odpowiedz

26. Kristoff

    I am running a large WooCommerce store and was receiving 500 internal server error on most front end pages & WP admin login. The store resides on a dedicated cloud server and had been running fast without fault for a few months. Tried ht access remedy firstly, but nothing changed, php memory should not have been a problem as I had increased this on install & I did not think WP ftp core files were corrupted, so looked elsewhere. Ran putty to connect to dedicate linux server and command line was showing huge CPU usage for mysql – 90%. Previously in my WP development experience sql errors or high usage are database related, so via a combination of sql workbench to kill connections & php myadmin to repair database tables (I only repaired wp_options in this instance) I was able to fix the internal server problem. My point on all of this is – even though problem was flagged as internal server error, it was a database table repair (after table analysis) which cleared the error.

    Odpowiedz

    • sahni

      Can you write in detail how did you do fix wp_options

      Odpowiedz

27. Saheed

    Thanks a lot, deactivating plugins solved my issue

    Odpowiedz

28. Dan

    Hey Guys ,

    I have this problem right now with some site and it looks like it is because server is overloaded and website is on shared hosting, so keep an eye on that !

    Odpowiedz

    • Janus

      Thanks i think you are right, i tried all above solutions but nothing helped, and i have pinge my site to a lot of search engines today so can be robots from there that have made the error.

      Odpowiedz

29. Julian

    Thank you! Deactivating the plugins vía PhpMyAdmin worked for me!

    Odpowiedz

30. Monayam Ahmad

    Not work for me. I face this problem when I want to customize my theme. Everything goes well. But to do 'customize’ I get this error. I don’t why.

    Odpowiedz

31. Ben

    Thank you very much for this very helpful article !
    The htaccess renaming worked for me ! Yeah !

    Odpowiedz

32. Joe

    Thank you so much! I was encountering endless Internal Server Errors for about 36 painful hours, and deleting/reuploading my theme via FTP then renaming the .htaccess file SAVED ME SO MUCH!
    You are a life saver.

    Odpowiedz

33. oladayo

    Thank you very much. it was the option of re-uploading the wp-admin and include folders that saved me after about 3weeks of troubleshooting.

    Odpowiedz

34. Rod Salm

    For me, it was the permissions setting for the entire directory. It needed to be 750. Soon as I changed that in the File Manager in cPanel it was back up.

    I didn’t figure that out on my own.

    Rod

    Odpowiedz

35. Giorgio

    Thank you so much! You save me from an heart attack…
    Simply I have renamed, via FTP, the .htaccess in .htaccess_old, and WP goes on.

    This is the new .htaccess, created as you suggested:

    # BEGIN WordPress

    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    This is the .htaccess that I find in my FTP and renamed in .htaccess_old:

    ## BEGIN WordPress<
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]

    # END WordPress

    I don’t know what had modify the file. Someone have an answer?
    Thank you!

    Odpowiedz

    • Donny

      I think it is a # problem, because your old file has 2 # and the new 1 # in the beginning.

      Hope it helped

      Odpowiedz

36. Oderinde Taiwo Martins

    I just want to say a big thank you to you guys. You saved my day with this article. I’m bookmarking this website now as I know I will have to come back and learn more from your resources. Thanks a bunch.

    Odpowiedz

37. Rionize

    tkank’s guys every thing is on .htaccess file and pemalink in word press check it out!!!

    Odpowiedz

38. Petrus Rex

    I had this issue after a fresh install of Wordpress. I would get this error specifically when accessing the plugins from my dashboard it turned out to be a corrupt .htaccess file but had to be handled server side by my web host. I’m running on Arvixe.

    Odpowiedz

    • abbas

      thanks

      Odpowiedz

39. Ivan Aliku

    I must give kudos to the moderators and content developers of this blog. I’ve not regreted knowing this website for one bit. The .htaccess solved the problem for me with ease. Keep up the good work.

    Odpowiedz

40. Being Khan

    I can’t rename it even.

    Odpowiedz

    • Petrus Rex

      You can change the name with an FTP client after you transfer it to your web host.

      Odpowiedz

41. Usman Aslam

    Thanks a lot, it was due to a bad plugin I couldn’t login, Wouldn’t have been possible without reading this. Great work … !

    Odpowiedz

42. Larah31

    Thanks man.. You’re the best

    Odpowiedz

43. Cory

    Thanks, renaming .htaccess to .htaccess.old did the trick :).

    Odpowiedz

44. Mitch

    I’ve got a weird one. My Internal Server Errors only happen on „Posts”, and Not on „Pages”. The host just updated the PHP version as well as the memory limit, and I re-uploaded the wp-admin and wp-admin files. No luck. Any other ideas?

    Odpowiedz

    • James

      I have the same issue. None of these things fixed it for me either.

      Odpowiedz

45. josh

    thanks this was helpful

    Odpowiedz

46. mark

    .htaccess did the thing for me. Thanks!

    Odpowiedz

47. Juan mejia

    Thanks!!!! htaccess in my case.

    Odpowiedz

48. Cachi

    Thanks, It solved in my case. Just delete de .htaccess , reload, and a new .htaccess file was generated and the site works !

    Thank you again

    Odpowiedz

49. Rochelle

    I have been in touch with my hosting provider two times and they have no idea what it is. They switched databases, thought it was hacked, and the other guy couldn’t figure out why I was having problems at all.

    Someone pointed me to your article (thank heavens) I did the htaccess file change and it helped it for two minutes. Then I did the php memory thing and that helped for a few minutes as well, then back to the internal server error. I’m currently working on trying to figure out if it’s a plugin. If that doesn’t help… then I’ll do the core files. And then after that… I have no idea. I guess I’ll try my hosting provider again.

    Would switching hosts be of any help at all?

    Odpowiedz

    • WPBeginner Support

      If all these steps don’t help and your host is unable to assist, then yes you can consider switching to a better WordPress hosting.

      Odpowiedz

      Administrator

50. Adela

    Thank you so much for so complet information!
    It was a plugin problem for me, impossible to find without your help!

    Odpowiedz