[GH-ISSUE #178] Clock offset fetch failed #107

Closed
opened 2026-02-27 19:28:26 +03:00 by kerem · 1 comment
Owner

Originally created by @kkerssem on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/178

I'm seeing this message in the debug log:

[2026-02-22T14:08:01.546Z][DEBUG][Http|AdminApi] [message="read ECONNRESET"] clock offset fetch failed

Quick search in the code shows that the fetchClockOffset() function is doing a HTTPS GET to https://worldtimeapi.org/api/timezone/Etc/UTC, which always results in a "connection reset by peer". Seems that the website is / has been down for most of the time recently. Maybe the time.now service is a valid alternative?

Originally created by @kkerssem on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/178 I'm seeing this message in the debug log: `[2026-02-22T14:08:01.546Z][DEBUG][Http|AdminApi] [message="read ECONNRESET"] clock offset fetch failed` Quick search in the code shows that the fetchClockOffset() function is doing a HTTPS GET to https://worldtimeapi.org/api/timezone/Etc/UTC, which always results in a "connection reset by peer". Seems that the website is / has been down for most of the time recently. Maybe the [time.now](https://time.now/developer) service is a valid alternative?
kerem closed this issue 2026-02-27 19:28:26 +03:00
Author
Owner

@rudyberends commented on GitHub (Feb 22, 2026):

Good catch, and thanks for reporting it. fixed in 9573a61

<!-- gh-comment-id:3941098561 --> @rudyberends commented on GitHub (Feb 22, 2026): Good catch, and thanks for reporting it. fixed in 9573a61
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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
starred/lox-audioserver#107
No description provided.