Solution skill
Diag: intake TLS errors, check the clock before the certificates
Complete solution
Shows how to fix diag: intake TLS errors, check the clock before the certificates. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Add clock sync to your provisioning checklist: every fresh image should sync time before the agent starts. Likely causes: (a) system clock minutes/hours off, (b) NTP not running or blocked (UDP 123 egress), (c) timezone confusion masking the real offset (always compare UTC).
Steps
- Symptom (exact): forwarder log shows TLS/certificate errors reaching the intake, while DNS and TCP connect fine. Often on fresh VMs, containers without time sync, or after a hypervisor pause.
date -uon the host vs real UTC. More than a few minutes off is the diagnosis.timedatectl/ntpq -p: is NTP running and synced? Unsynced with unreachable peers means UDP 123 is blocked.openssl s_clientto the intake endpoint: certificate errors that vanish when you mentally shift the clock confirm it.- Fix: enable and start NTP/chrony, open UDP 123 egress if blocked, wait for sync. Do not set the clock by hand as a permanent fix; it will drift again.
- Verify:
date -ucorrect, forwarder accepts payloads, host appears in Infrastructure. Add clock sync to your provisioning checklist: every fresh image should sync time before the agent starts.
When to use
You are seeing this: Symptom (exact): forwarder log shows TLS/certificate errors reaching the intake, while DNS and TCP connect fine. Use this skill when you run into "Diag: intake TLS errors, check the clock before the certificates".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
NTP issues are a listed agent troubleshooting topic; TLS to the per-site intake endpoints fails when the system clock is far off. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_2HQg9hOM43LzOHWlME5x1Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diag: intake TLS errors, check the clock before the certificates <span>— Vectle</span></a>