Page 1 of 1

Internal Server Error (500)

Posted: Wed Aug 30, 2017 5:46 am
by Two8nine
Hoping someone can help with this. Have been using TimeTrex for about a year now without issue. This morning all users see a popup with the following text:

The network connection was lost. Please check your network connection then try again.

Error: error "Internal Server Error"

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@example.com to inform them of the time this error occurred, and teh action you performed just before this error.

More information about this error may be available in the server error log.

(500)

--------------------------------------------

No changes have been made within the last week (Though a manual upgrade was done within the past month.)

We are using community edition 10.7.1, and it is an automated install.

The OS Timetrex is installed on is Windows 10.1 -- though the issue occurs for all users (Windows 7/Windows 10) on all browsers tested. (IE, Firefox, Chrome).

Closing the error does seem to allow for normal operation, though it re-occurs every time the page is loaded.

Re: Internal Server Error (500)

Posted: Wed Aug 30, 2017 7:08 am
by shaunw
We will need to see the TimeTrex log file to get more information, in your TimeTrex.ini.php file, set the following under the [debug] section:
enable = TRUE
enable_display = FALSE
buffer_output = TRUE
enable_log = TRUE
verbosity = 10

Then reproduce the error and attach the log file here.

Re: Internal Server Error (500)

Posted: Wed Aug 30, 2017 7:50 am
by Two8nine
I've attached the log.

Re: Internal Server Error (500)

Posted: Wed Aug 30, 2017 12:51 pm
by Two8nine
To update the issue appears to have self-corrected. Would still appreciate any thoughts as to the cause however, as I'm concerned something behind the scenes isn't quite right.

Re: Internal Server Error (500)

Posted: Wed Aug 30, 2017 1:45 pm
by shaunw
Can you attach a copy of your c:\timetrex\apache2\log\error.log* files as well? They may provide more information too.