Geotab Support Forum

Hello

How do I know which version of checkmate is fully stable and can be deployed?

I installed checkmate 5.3.1 Build 11640 on a completely new machine, but got errors when using http://servername" target="_blank" rel="nofollow">http://servername," target="_blank" rel="nofollow">http://servername" target="_blank" rel="nofollow">http://servername, after enabling Web Server. As I previously tested that 11640 was good, I uninstalled build 11640, installed build 11341, and enabled web server again. (host, and security configs were previously configured in build 11640). http://servername" target="_blank" rel="nofollow">http://servername was successfull in build 11341.

I then unistalled build 11341 to install build 11640 again, and now http://servername" target="_blank" rel="nofollow">http://servername is working fine.

All this long story is to tell you that you probably missed out some components in later builds. Please ensure to include them in latest builds.

Where can we download/test/use checkmate 5.4

Thank you

The only version that is fully tested is the one that can be found at checkmate.geotab.com
At this point the version is 5.3.1.10905.

Any builds found on our latest build site has not gone through human testing, only machine testing and, however unlikely, may contain some small errors.

As for 5.4, this is only available through my.geotab.com. If you wish to use/test it you can try our demo which is found here

Hi again

Found something else on build 11640, but did not test on later version. I had a look at latest release and the issie has not been raised.

I configured email notification and enable SSL on port 587. Get mail successfully. However, after a server restart, the SSL port comes back to the default 25, and as such, main notification fails. Changing back to port 587 solves the problem. Probably the port is saved only in memory, and needs to be saved on disk.

This was good in older versions (11341 i think)

Thank you

I have tested this myself and confirmed the issue with the latest builds. I have sent a case to the developers so that they can look into it.

This issue has been resolved by the developers as of build 12373.