Joomla 1.7 Administrator Internal Server Error
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 your site joomla error 500 internal server error / issues on your restored site NextCommon issues on restored sites and how to joomla http error 500 solve them You have to make sure that there are no settings transferred in files from your old server which joomla server error 500 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 https://forum.joomla.org/viewtopic.php?t=296527 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 move your site to a https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html 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 same problem could be caused by your .htaccess file. It's always
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 bug https://www.yireo.com/tutorials/magebridge/troubleshooting/1245-solving-500-internal-server-errors 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 in server error ‘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 tickets before internal server error 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 your time and efforts. Monday
error in some hosting environments is the 500 Internal Server Error. It hides the actual PHP error, and tells you to contact the system administrator. This tutorial helps you to solve these errors. Written by Jisse Reitsma Written by Jisse Reitsma Jisse is the founder of Yireo and lead developer of numerous Yireo extensions for Joomla, Magento and MageBridge. He is also the author of the authoritive book Programming Joomla Plugins. He is also proud to be a member of the Zend Z Team. What happens? Every time that a 500 Internal Server Error occurs, you should take the guidance in that error literally: You should contact the system administrator of the hosting environment to report the real error to you. Internally something went wrong, and as long as the real error is not fetched, everybody will be clueless. These types of problems specifically occur in hosting environments that use some kind of CGI-interface to PHP (CGI, FCCGI, FastCGI, suPHP). It could be that something went wrong on the configuration-level, but it might also be that PHP encountered some kind of PHP Fatal Error. In all cases, fetching the actual log from the logfiles is vital. Note that - unless you have root-privileges - it is likely that you don't have access to these log-files. Therefor, contact the hosting provider. Make sure errors are logged Not all hosting environments are actually prepared for logging errors - it sounds stupid, but is sometimes configured as such for ridiculous reasons like saving disk space. The following PHP-settings are a good start for logging: log_errors = On
error_reporting = E_ALL & ~E_DEPRECATED
display_errors = On Note that these settings might be bad in production environments. After debugging, it's best to restore the original settings. Wrong file permissions One common cause for a 500 Internal Server Error are the file permissions of PHP-scripts. In general, all files for MageBridge should have the same file permissions as the other Joomla! files and/or Magento files. A 500-error might be thrown if the file permissions are considered to be dangerous: The execution bit should never be used on PHP-files (755 or 777 or something alike), but some servers also object against the PHP-file being world-writable (666 or 777). File permissions like these can be set either through SSH or FTP. A lot of times, Magento is causing headaches here, not Joomla!. I