That’s something I didn’t expect.
That message either comes because some nonce id in the packet is indeed invalid or a lot of time passed since the nonce was generated. Probably I should detail that message. I don’t think I encountered such thing before, though.
Probably the log above those messages would be helpful.
I’ll look more over the code tomorrow trying to figure out what could go wrong.