Below are two examples of how the problem can occur:
A user in New York leaves the timezone setting as Pacific Standard Time (PST), which is 3 hours off from Eastern Standard Time (EST), which applies in New York. To compensate for that, he or she adjusts the time in his/her computer to be 3 hours later than what the PST time is.
A user does not enable the Daylight Saving Time option in his or her computer, but manually adjusts the time by one hour to compensate for the start of Daylight Saving Time.
The problem with either of the scenarios above, is that the computer continues to operate internally with the time based on the timezone and Daylight Saving Time adjustment that apply to the system settings. As a result, users who do these can have problems when their computers and the servers disagree as to what the actual time is. That can be the case with certificates because they are date and time sensitive.
Since you are seeing the problem exclusively in Chrome, the issue might be the timezone setting in Chrome. To check that, click the 3-bar icon in the upper right hand corner of the Chrome screen, select "Settings," and type "time" in the Settings page search bar.