Http 500 Internal Server Error Joomla Administrator
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this joomla server error 500 site About Us Learn more about Stack Overflow the company Business Learn joomla http error 500 more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x
Joomla Error 500 Internal Server Error
Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up 500 https://forum.joomla.org/viewtopic.php?t=296527 internal server error at back end - Joomla up vote 10 down vote favorite 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 is working fine in Local server. Please suggestion me any solution. Thanks in advance. joomla joomla1.7 share|improve this question edited Nov 22 '11 at http://stackoverflow.com/questions/8225027/500-internal-server-error-at-back-end-joomla 10:08 nfechner 12.3k43057 asked Nov 22 '11 at 10:05 Dheeraj Agrawal 55441324 Did the logfiles show anything? –nfechner Nov 22 '11 at 10:08 thankx for the reply.... and log is not showing anything :( –Dheeraj Agrawal Nov 22 '11 at 10:48 2 The apache error.log (if you are using apache) should show at least something. –nfechner Nov 22 '11 at 10:52 Can you add a little more info? How did you place the files on the server initially - unzip locally and ftp individual files to server, install locally an transfer with akeeba backup .jpa file(s) or manually unzipping on the remote server? Is the error as soon as you go to /administrator/, as soon as you successfully login, or when you go to one specific page within the admin area? Depending upon your server's setup you may need the apache error log, or perhaps suexec's error log file. –Dean Marshall Nov 23 '11 at 2:40 Have you tried a different browser? I know this sounds like madness but I've just been helping someone on the Joomla forums and one particula
TroubleshooterAkeeba Backup for Joomla!Admin ToolsAkeeba Solo (Standalone)Akeeba Backup for WordPressTicket SystemKickstartRemote CLIUNiTEWalkthroughsWarningsJSON APIVideos Username Password Two Factor Authentication Key Remember Me Log in Forgot your username? Forgot your password? HomeDocsTroubleshooter Common issues on restored sites and how to solve themPrev Troubleshooting issues after restoring your site / issues on your restored site NextCommon https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html issues on restored sites and how to solve them You have to make sure that there are no settings transferred in files from your old server which are not compatible with your new host. The most notable culprits are .htaccess and local php.ini directives. If your site was using Admin Tools' .htaccess Maker If you have used Admin Tools' .htaccess Maker please remember that after restoring the site to a different location server error you will need to reconfigure and create a new .htaccess. Login to the back-end of your site, go to Components, Admin Tools, .htaccess Maker, then change the domain and directory names at the bottom of the page and finally click on Save & Create .htaccess. This is mandatory, every time you move your site to a different host, domain name, subdomain or directory. I can't log in to my site after I restored internal server error it to a new location This is a very common mistake with Joomla! 1.6/1.7 and later versions. What you probably not remember is that you modified the cookie setup parameters in your site's Global Configuration page. The thing is, if you modify the cookie domain name and/or path, it's very likely that you will no longer be able to log in to your site if the domain name, subdomain or directory changes - exactly what happens when you restore a site to anywhere except its original location! Luckily, the workaround is very simple. Please edit the configuration.php file in the root of your site and find the lines starting with public $cookie_domain and public $cookie_path. Modify them so that they read: public $cookie_domain = ''; public $cookie_path = ''; Save the file, clear your browser's cookies and cache, quit and restart your browser and try logging in to your site. You should be able to login without any problem now. Another thing that you should be aware of is that the same problem could be caused by your .htaccess file. It's always a good idea to at least temporarily rename .htaccess to something else (e.g. htaccess.bak) when you're trying to troubleshoot a login issue. A .htaccess file may define redirections which get in the way during login