Joomla 2.5 Internal Server Error Administrator
Contents |
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 joomla server error 500 your site / issues on your restored site NextCommon issues on restored sites and
Joomla 500 Internal Server Error After Migration
how to solve them You have to make sure that there are no settings transferred in files from your old
Joomla Http Error 500
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 http://forum.joomla.org/viewtopic.php?t=344518&start=30 Admin Tools' .htaccess Maker please remember that after restoring the site to a different location 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 https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html move your site to a different host, domain name, subdomain or directory. I can't log in to my site after I restored 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
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? You need to be a subscriber https://www.akeebabackup.com/support/site-restoration/14664-500-internal-server-error-when-accessing-backend.html in order to receive support. If you want to report a http://joomladetroit.com/joomla-tutorials/index-php-error-500-with-htaccess-solved bug or ask a pre-sales question, you don't have to be a subscriber. Just use the Contact Us link at the footer of the site. Subscribe HomeSupportSite restoration#14664: 500 Internal server error when accessing backend #14664 – 500 Internal server error when accessing backend Posted server error in ‘Site restoration’ This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information. Monday, 14 January 2013 07:26 CST IThypercube AKEEBABACKUP, ADMINTOOLS Mandatory information about my setup: Have I read the related troubleshooter articles above before posting (which pages?)? Yes Have I searched the internal server error tickets before posting? Yes Have I read the documentation before posting (which pages?)? Yes Joomla! version: Joomla! 2.5.8 Stable [ Ember ] PHP version: 5.3.20 MySQL version: 5.5.23 Host: (optional, but it helps us help you) Hostgator, Letshost.ie Akeeba Backup version which took the backup: 3.6.12 Pro Kickstart version used to extract the backup: Kickstart Core 3.6.0 Description of my issue: Unable to access backend side of site. Front-end works perfectly. Error message when accessing the back-end page:---------Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.Please contact the server administrator, webmaster@freetechhelper.com 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 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache Server at www.freetechhelper.com Port 80 ------------- No errors during creating and extraction of backup. Thanks in advance for
What's a Joomla User Group? Speakers, Sponsors & Partners Organizers and Facilitators Site Hosting by CloudAccess.net Resources Joomla Webinars How to setup a Joomla Day Event Search... Index.php Error 500 with .htaccess [solved] Details Written by Son Koral Published on 27 May 2013 Category: Joomla Tutorials Print Email One of the more frustrating things admins seem to encounter with Joomla is trying to get rid of the "/index.php/" from Joomla URLs. There are some server configurations that will throw a Error 500 Internal Server Error / Server Misconfigured page when you move htaccess.txt to .htaccess, but fear not! Rather than go into *WHY* this is happening, here's how to solve the issue: After changing htaccess.txt to .htaccess, open the .htaccess file in the root folder of your Joomla install with a text editor. Close to the top, you should see this part: ##
# READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE!
#
# The line just below this section: 'Options +FollowSymLinks' may cause problems
# with some server configurations. It is required for use of mod_rewrite, but may already
# be set by your server administrator in a way that dissallows changing it in
# your .htaccess file. If using it causes your server to error out, comment it out (add # to
# beginning of line), reload your site in your browser and test your sef url's. If they work,
# it has been set by your server administrator and you do not need it set here.
#### Can be commented out if causes errors, see notes above.
Options +FollowSymLinks ## Mod_rewrite in use. RewriteEngine On Go to the line "Options +FollowSymLinks" and add a "#" to comment it out as below. #Options +FollowSymLinks Your Joomla site should now work correctly without the "/index.php/". Looking for other Joomla Resources? Don't waste your time searching for hours on the JED! Check out our trusted Joomla Resourcespage! < Prev Next > Comments People in this conversation 10 Comments | Ad