Hm… Initial clock anomalies are one of the known glitches of the new (and still fairly experimental, last I heard) suspend feature:
I was able to trigger a clock mismatch once, when SSHing into a suspended Machine right after fly m start, but it took several tries…
Anyway, it looks like it should be adequate to just wait a few more seconds after bumping into this—and then try SSH again (?).