Jump to content

CodeRider

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

Profile Information

  • First Name
    Code
  • Last Name
    Rider

CodeRider's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • One Year In Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

1

Reputation

  1. CodeRider
    Hi Prestashop Windows&Apache Users Same infinite loop with Prestashop 1.7 installation on Apache 2.4, PHP 7.1.3 on Windows Server 2012 R2 Datacenter. Solution: activate extension php_curl.dll in php.ini and restart Apache. Hope it helps.
  2. CodeRider started following PS 1.7 Install leads to an infinite redirect loop
  3. CodeRider
    In one case Smarty setting caused the error. Check if In Advanced Parameters-Performance 'Template Compilation' is set to 'Never recompile template files' If not, set it to this value.
  4. CodeRider
    You have Apache on Linux. So you can't go that way. But the 500 can be result of a timeout anyway. So have a look in your configuration where it can happen.
  5. CodeRider
    Hi locen I wrote where to change it if you use IIS and have access to it. Otherwise you have to ask your hosting partner who should be able to identify the origin of the error. What is your webserver version, PHP version etc.?
  6. CodeRider
    Hi all, The cause of Internal Server Error 500 can be too low values for activity and request timeout in FastCGI setting on IIS. When using IIS you can activate Failed Request Tracing Rules for your website and define a rule for only this error to analyze the exact reason. Start IIS Manager, open server-sites-your site and click Failed Request Tracing in the actions pane. Activate it and check if the path for logfiles is ok. Now click Failed Request Tracing Rules and add a rule. Select All Content (*), next select Status Code and enter 500 (400-500 is also possible), do not select Time taken and Event severity, next select only WWW Server and Area RequestNotifications (other areas can be added later if necessary). Save the rule and try to get the 500 error. If the 500 error occurs it is logged and you can view the log with your browser. You find it in the path defined in Failed Request Tracing for your site. In the Request Summary you will see the module causing the error. In case FastCgiModule is the reason you can change the setting in IIS. Select the server (not your site) and there you have FastCGI setting. You can see that you can select that this module shall generate a 500 error. Select the PHP version of your site and increase activity and request timeout. You can calculate it from the logfile or test with some values. Good luck
×
×
  • Create New...