We have been using sh404SEF- editor’s choice and the most popular one until recently. It is a business, the Joomla component that used to generate search engine friendly urls and was the free, all of sudden the genius guys or the makers of sh404SEF turned out to go business, the component was charged 35$ for a single access for a year. So, we decided to drop out sh404SEF and suggest those conscious people like us NOT to use sh404SEF simply because there are several other free Joomla components for generating Search Engine Friendly URLs.
The Internal Server Error we received, by chance, happened to be after the case of sh404 above. But might not be the one due to that component. Below is the exact copy of what is displayed on our website pages.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
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.
Apache/2.2.13 (Unix) mod_ssl/2.2.13 OpenSSL/0.9.8k DAV/2 mod_auth_passthrough/2.1 FrontPage/18.104.22.16835 Server at ekendraonline.com Port 80
Now, let’s explore and study to fix the problem. Since this is a server problem or the server configuration problem in our host (Bluehost), we will be dealing with the same. We are taking about Linux hosting only. (unsure about other hosting platforms)
The first thing you need to fix or check if 500 Internal Server Error can be handled is to rename the server configuration file htaccess.txt to .htaccess only (simply right click the file htaccess.txt to rename and modify to .htaccess) in the file manager of the cPanel (we guess).
The problem is most likely to be an issue with DOS carriage returns / line feeds versus what the Linux server expected. There are various tools create .htaccess files online, but generally notepad or any text editor will do the work. Ensure to test your site thoroughly after making an adjustments to the .htaccess file.
And remember to hackup the file htaccess.txt before acting.