500 internal server error at back end - Joomla

Question

I have installed new site in Joomla 1.7 and its working fine, but when i checked its back-end (administrator) got 500 Internal Server Error.

Note: Site

Answer 1

In my case there was a single file with bad permissions.

It can be tricky to figure out which file has the problem so just run this to set the permissions for all the files in the directory:

chmod -R ug+rwX .
chmod -R o+rX .

Answer 2

I also have the same issue on my site backend when editing or saving some articles, modules etc...Finally i solved it... Add these lines to /etc/httpd/conf.d/mod_secuirity.conf on your server

SecRuleEngine Off

save it...and restart apache...it works fine for me. Adding these lines disable mod_secuirity engine off.I don't know if it causes secuirity problems in future.. Tnx all...

Answer 3

First you have change folder permission to 775 for the following folders:

cache, logs, tmp & administrator/cache

then go to: configuration.php

find code:

$log_path = 'XXXXXXXXXXXXX';
$tmp_path = 'XXXXXXXXXXXXX';

and change code into:

$log_path = './logs';
$tmp_path = './tmp';

problem solved :)

Answer 4

I had this problem, but none of your advices didn't help.
I fixed a problem only after I switched off all modules via PhpMyAdmin (PMA).

Table modules, changed parameter "published" to 0 for all and then enabled only few modules with these types:

• mod_login
• mod_menu
• mod_sumbenu
• mod_toolbar
• mod_title

After this I entered admin page and used top menu to enable all needed modules one by one. After admin page started to give me 500 error again I knew what module is faulty and I disabled it again via PMA.

Answer 5

I tried all the above ideas. Without avail. For my site (which was an outdated Joomla 1.5.x site- don't ask!!!), where the backend suddenly stopped working, the final solution was switching the servers PHP version from 4 to 5.5 (even 5.4 did not work!).

I then got some strange PHP warnings in the frontend. But I then updated Joomla from the now again working backend to the last 1.5 version and everything worked fine from the on.

Phew! Maybe this helps someone later on...

Answer 6

Try reinstalling database with the correct compatibility and also check web.config file on ftp for correct configuration paths !