We have been using a version of Timetrex Community Edition, installed on an AWS EC2 instance. It's been running fine for about 2 years. About a month ago we got a message in the header of the Web GUI "Auto Update failed, contact your Admin".
As it was still working otherwise, we let it slide until yesterday, when it stopped working completely with an error msg "TimeTrex is unable to connect to its database, please make sure that the database service on your own local TimeTrex server has been started and is running."
We tried updating to the current version, re-named the old directory, and did a fresh ZIP file installation with the old .ini file copied over, but are now getting the same error as before. Upon trying to troubleshoot, we identified a couple of anomalies.
It seems to be unable to talk to the Postgres Database server for some reason. No other configurations on our server were changed prior to the error. We also tried disabling the firewall on the server, but to no avail. We had upgraded PHP version from 7.0 to 7.3.11 recently, but retrograding didn't fix the problem (and I believe it was still working for a day or two after the upgrade.)
I've attached some screen shots showing the TimeTrex troubleshooting window with the 4 pertinent error messages. It is saying the required PHP extensions: PostgreSQL, BCMATH, and SOAP are not installed and need to be enabled. But when we look at our server (see screen shot attached), they appear to be present and enabled... also it complains about the file permissions of the timetrex.ini file. We tried opening up all the way the permissions to that as well, but still got the error. Also, curiously, the hyperlink at the bottom of the install wizard "Detailed PHP information" doesn't display any info, just takes us back in a circular loop to the same screen.
We created a test file "info.123.php" to test communication with the database, and it does not see those missing extensions either, so obviously troubleshooting that should solve 3/4 of the problems for Timetrex, leaving the permissions issue to resolve.
We're probably just missing something stupid (as we are not system admin experts...)
If this is something you can help us solve, please let me know. Also, I noticed you have WooCommerce background. We are just now launching a WooCommerce store, and independent of (and after) this Timetrex issue, I'm looking for some WooCommerce support.
FYI, I'm in Chicago. I look forward to hearing back from you.
