Another issue I spent hours on. I usually run into some trouble when rebooting the docker server that has the Only Office Document Server container running on it, usually just need to get the new JWT token and paste it in my NextCloud / OnlyOffice settings.
This was not the error I was used to… and it took hours to figure out and it had nothing to do with the Only Office Document server container. I was at the point of trying any little fix someone mentioned and one post… one post among the large number of listings online had a small quibble about the time and a hacky fix of going into the php code of the NextCloud server to change the “leeway” it would allow. I was like no way, but I checked the time on my document server and web server and it was off four minutes.
Anyway, this is also when I found out that NTP was blocked on my VPS host, well at least “legacy UDP port 123 NTP” services were blocked. Apparently there are some vectors there that are not worth dealing with and I did not want to fill out a ticket to have them unblock it to my host.
I looked around and found that the new hotness in time sync is using http sync against a known good server like google.com. The htpdate package does the trick and after syncing both host against google.com the error disappeared.
TLDR: Check your clocks.