Hikashop 500 Error when I use Akeeba Admin Tools

  • Posts: 35
  • Thank you received: 1
10 years 5 months ago #158655

-- url of the page with the problem -- : goldsmiths.accountsupport.com
-- HikaShop version -- : HikaShop Business: 2.3.0
-- Joomla version -- : 3.3.0
-- PHP version -- : 5.3.13
-- Browser(s) name and version -- : all
-- Error-message(debug-mod must be tuned on) -- : 500 internal server error

Hello,

I have an issue that I have been trying to seek help with through Akeeba but not getting anywhere with them and thought maybe I can find an answer here on my issue.

I want to enhance the security of my site using Akeeba Admin Tools Pro which has a .htaccess Maker that allows you to harden a sites access by creating a custom .htaccess file. the Admin Tools .htaccess Maker seems to work great on the site until I try to navigate to any pages related with Hikashop?

When I try to go to any hikashop page I get a 500 internal server error when I generate a .htaccess file through Akeeba Admin Tools. Akeeba support said to deactivate all rules in the Maker until I find the setting that is causing the issue. The only problem with that is I basically turned them all off so it is pretty much identical to the .htaccess file that comes out of the box with Joomla. Yet I still get the 500 internal server errors?

Do you have any thoughts as to why this could be causing the custom .htaccess file to kick out 500 internal server error pages for hikashop pages only? Could it be related to the built in SEF settings in hikashop perhaps?

Thank you for your time!

Sincerely,
Brandon Cardone, Card One Concepts

Please Log in or Create an account to join the conversation.

  • Posts: 82910
  • Thank you received: 13379
  • MODERATOR
10 years 5 months ago #158844

Hi,

Take the htaccess.txt at the root of your website, or in a brand new Joomla installation package and replace your current .htaccess with it.
That should fix the 500 error if it comes from that.
Otherwise, it means that there is a PHP error and you should look in your PHP error log of your web server for the error message relative to the crash of the processing. That will give valuable information on what's going on.

Security components can potentially detect false positives (thinking that a request is an attack because it detected something in the request which is actually not a security problem). To avoid these only two solutions: either deactivate the security check which causes the problem and modify the code of the security component to not trigger that false positive detection.

The following user(s) said Thank You: CardOneConcepts

Please Log in or Create an account to join the conversation.

  • Posts: 35
  • Thank you received: 1
10 years 5 months ago #159262

Thank you for your assistance on this. It turn out it was a setting in the akeeba htaccess maker causing the issue. This has been resolved.

Thank you for your time!

Sincerely,
Brandon Cardone, Card One Concepts
Last edit: 10 years 5 months ago by CardOneConcepts.

Please Log in or Create an account to join the conversation.

Time to create page: 0.052 seconds
Powered by Kunena Forum