Force NTP when starting bot #13

Open
opened 2024-07-23 11:58:27 +00:00 by eloy · 1 comment
Contributor

The bot gives weird errors if the system time is very wrong. I only discovered this while trying to clone the repo again and it said the certificate expired.

It could print the current timestamp on startup so it is clear something is wrong.

The bot gives weird errors if the system time is *very* wrong. I only discovered this while trying to clone the repo again and it said the certificate expired. It could print the current timestamp on startup so it is clear something is wrong.
Owner

I assume this is because the certificate of api.telegram.org is not valid when the system time is wrong. There is no way to force NTP especially without root permissions and i believe it's out of the scope. This said, reporting it at startup could be interesting.

I assume this is because the certificate of api.telegram.org is not valid when the system time is wrong. There is no way to force NTP especially without root permissions and i believe it's out of the scope. This said, reporting it at startup could be interesting.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: foxo/printer_bot#13
No description provided.