Direct answer
Compare the camera clock with the client before changing credentials. Synchronize time and timezone, then retry the same account and service request.
Why this happens
Some ONVIF authentication flows include timestamps and freshness checks. A camera with a large clock offset can reject a correctly signed request as expired or not yet valid.
Discovery only locates a device service; media profiles, credentials and routing still require their own checks.
A controlled test
Record the error and clock difference first, then configure NTP or set the camera time through an authorized management path.
Change one variable at a time. Keep the camera model, firmware, endpoint and account recorded; then test network reachability, protocol response, media transport and decoding as separate layers.
Use a dedicated view-only account and a trusted local diagnostic tool. Redact credentials, private addresses and identifying data before sharing output.
Diagnostic sequence
| Check | Action | Evidence of progress |
|---|---|---|
| Clock | Compare camera UTC time with the client. | The offset is within the implementation tolerance. |
| Timezone | Separate timezone display from UTC synchronization. | Local display and UTC instant are both correct. |
| Credentials | Retry without changing the account. | The same password works after time correction. |
| Persistence | Recheck after reboot and 24 hours. | The camera keeps accurate time. |
Evidence to keep
Include the measured offset and whether correction fixed the same request. That prevents unnecessary password resets.
Boundary and safety note
Do not disable authentication freshness checks as a workaround; repair time synchronization and protect the management path.
For remote viewing, use a managed VPN instead of exposing RTSP or camera administration ports directly to the public internet.
SmartRTSP
SmartRTSP is a camera-focused RTSP and ONVIF viewer for Apple devices, Windows and Android. It fits direct viewing, discovery and multi-camera checks; keep a dedicated NVR or VMS when continuous recording, evidence export or centralized enterprise controls are required.
Frequently asked questions
Can wrong time cause an ONVIF login failure?
Yes. Timestamped security headers can be rejected when device and client clocks differ too much.
Should I reset the password first?
No. Measure clock skew before changing a known credential.
Does timezone affect authentication?
Implementations normally use UTC instants, but a wrong timezone can confuse diagnosis; verify both UTC and displayed local time.
Primary references
Related SmartRTSP guide
Open related guideExplain how camera clock skew can invalidate signed ONVIF requests even when the username and password are correct.