• From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Topic: 500 Error After Logging In (After Upgrade to 2.3.14)

I just finished updating to version 2.3.14 and now when I login I get a 500 error:

---------
500 Internal Server Error

The page cannot be displayed.
---------

When I refresh the page (which requires resending the data), FA loads correctly and everything seems to be working.  I followed the instructions on the Wiki to the letter.  The only change to config.php was the addition of the default_orientation variable.  I also added a bcc_address to the company setup.  Other than that, everything is as it was before.

Any idea how to get rid of this error message?

Thanks!

Regards,

Chris

P.S.  The upgrade looks pretty good!  I particularly like the new functionality to select the report orientation.... very nice!

chrison's Website

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,150

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Which version are you upgrading from?
What platform / hosting service is being used?

There is a cache issue introduced in v2.3.14 when adjusting the includes/session.inc for faillog protection (not because of faillog protection) and is a known issue for certain shared hosting that relies on numerous redirects (302 error).

Refer link for causes.

apmuthu's Website

  • From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

apmuthu wrote:

Which version are you upgrading from?

2.3.13

apmuthu wrote:

What platform / hosting service is being used?

My site is hosted by HostPapa.  Here's some info on their setup:

Operating system     linux
Architecture     x86_64
Kernel version     2.6.32-379.9.1.lve1.1.9.7.2.el6.x86_64
Apache version     2.2.23
PHP version     5.3.20
MySQL version     5.5.28-cll
Perl version     5.10.1

Btw, I have the following in my includes/session.inc file in case it's useful:

// ini_set('session.save_path', dirname(__FILE__).'/../tmp/');

ini_set('session.gc_maxlifetime', 36000); // 10hrs
ini_set('session.cache_limiter', 'nocache'); // prevent 'page expired' errors

$Session_manager = new SessionManager();
$Session_manager->sessionStart('FA'.md5(dirname(__FILE__)));

// this is to fix the "back-do-you-want-to-refresh" issue - thanx PHPFreaks
header("Cache-control: nocache");
apmuthu wrote:

There is a cache issue introduced in v2.3.14 when adjusting the includes/session.inc for faillog protection (not because of faillog protection) and is a known issue for certain shared hosting that relies on numerous redirects (302 error).

Refer link for causes.

Hopefully the info provided above will help someone track down the problem and fix it.  In the meantime, it's no big deal...  I'll just keep refreshing the page when I login.

Regards,

Chris

chrison's Website

  • From: Netherlands, Amsterdam
  • Registered: 03/06/2011
  • Posts: 111

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

seems to be there's a relation with my "302 error problem". I sometimes experience the same 500 error as described above.

https://frontaccounting.com/punbb/viewtopic.php?id=3767

  • From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

erwindebruin wrote:

seems to be there's a relation with my "302 error problem". I sometimes experience the same 500 error as described above.

https://frontaccounting.com/punbb/viewtopic.php?id=3767

Did you try the fix to includes/session.inc that was suggested?  If so, did it fix the problem?

Thanks!

Regards,

Chris

chrison's Website

  • From: Netherlands, Amsterdam
  • Registered: 03/06/2011
  • Posts: 111

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

no, i tried but it didn't fix the problem.

We are running an own webserver (controlled by Plesk software), so we are able to change any setting.

  • From: Netherlands, Amsterdam
  • Registered: 03/06/2011
  • Posts: 111

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

checked the server error log, it says:

[Sat Jan 19 11:28:49 2013] [error] [client #IPADRES#] malformed header from script. Bad header=HTTP 1.1 303 See Other: index.php, referer: http://#WEBSITE#/index.php

  • From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

In case it will help, I did a screenshot of the page info in Firefox for one of the instances when the login bombed with a 500 error.  Since I can't upload it here, it is available for viewing here.  As well, a search of the logs for my site found the following line:

70.67.201.56 - - [19/Jan/2013:12:23:46 -0500] "POST /accounting/ HTTP/1.1" 500 568 "https://www.crazychris.ca/accounting/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0"

Hope that is helpful to someone...

Regards,

Chris

chrison's Website

  • karyg
  • New member
  • Offline
  • Registered: 01/21/2013
  • Posts: 3

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

I am having the same issue with a fresh install...

Any solution to this yet?

  • joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,106

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Please try to change line 362 in /includes/session.inc from:

header("Cache-control: private");

to

header("Cache-control: no-cache");

and see if it helps.

/Joe

  • karyg
  • New member
  • Offline
  • Registered: 01/21/2013
  • Posts: 3

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Tried resetting cache control to 'private, no-cache' and 'no-cache' with no change.

It should be noted that refreshing the page gains access, so I'm getting logged in, just not getting to the page on submission of the login form.

  • From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

joe wrote:

Please try to change line 362 in /includes/session.inc from:

header("Cache-control: private");

to

header("Cache-control: no-cache");

and see if it helps.

/Joe

Did that.  No change.  sad  I still get the 500 error but when I refresh the page I get in.

Regards,

Chris

chrison's Website

  • From: Netherlands, Amsterdam
  • Registered: 03/06/2011
  • Posts: 111

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

I tried the same but no result.

  • joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,106

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Please replace your existing /includes/session.inc with this one from the newly updated HG repository.

It removed the error for me on a specific server.

/Joe

Post's attachments

session.inc 14.5 kb, 65 downloads since 2013-01-22 

You don't have the permssions to download the attachments of this post.
  • From: Netherlands, Amsterdam
  • Registered: 03/06/2011
  • Posts: 111

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

thnx it works for me!

  • From: Canada, BC, Lantzville
  • Registered: 01/07/2013
  • Posts: 135

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

That fixed it here, too.  Thanks!

Regards,

Chris

chrison's Website

  • karyg
  • New member
  • Offline
  • Registered: 01/21/2013
  • Posts: 3

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Thank you!

18 Reply by apmuthu (edited by apmuthu 01/27/2013 12:51:17 pm)

  • From: Singapore, India, Chennai
  • Registered: 05/02/2009
  • Posts: 6,150

Re: 500 Error After Logging In (After Upgrade to 2.3.14)

Great Janusz. Your HG Changesets 3155 and 3157 did the job.

apmuthu's Website