Printing always stops at midnight

Attached to a Geeetech A10 printer.....Octoprint always stops if midnight occurs during the print..

dont know if its the Octopi or A10 causing it....it just freezes....last part of the log:
2020-02-05 22:35:06,590 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-02-05 22:45:12,899 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-05 23:00:12,902 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-05 23:15:12,904 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-05 23:30:12,907 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-05 23:45:12,909 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-02-06 00:00:01,384 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.29
2020-02-06 00:00:01,412 - octoprint.server.util.sockjs - INFO - Client connection closed: ::ffff:192.168.0.157
2020-02-06 00:00:01,414 - tornado.application - ERROR - Exception in callback <functools.partial object at 0x711df9c0>
Traceback (most recent call last):
File "/home/pi/oprint/local/lib/python2.7/site-packages/tornado/ioloop.py", line 605, in _run_callback
ret = callback()
File "/home/pi/oprint/local/lib/python2.7/site-packages/tornado/stack_context.py", line 277, in null_wrapper
return fn(*args, **kwargs)
File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/vendor/sockjs/tornado/transports/websocket.py", line 94, in
self.server.io_loop.add_callback(lambda: self.send_pack(message, binary))
File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/vendor/sockjs/tornado/transports/websocket.py", line 89, in send_pack
self.write_message(message, binary)
File "/home/pi/oprint/local/lib/python2.7/site-packages/tornado/websocket.py", line 249, in write_message
raise WebSocketClosedError()
WebSocketClosedError
2020-02-06 00:00:01,550 - octoprint.server - INFO - Shutting down...

I'm guessing this is the client side of some conversation. As in, you have a smartphone app or something else remotely that's attached via sockets using JavaScript code. Maybe it's a tiny LED monitor device that shows print progress...?

If you are using something to connect remotely for monitoring status, it would be interesting to know if it connects via HTTPS (rather than HTTP). This would make the problem more of an SSL bug with respect to time and session keys and such.

It would be good to have the entire octoprint.log instead of just a part of it. Knowing the version of OctoPrint and other details from that log are crucial to helping you.