Troubleshooting
ONVIF camera not found on Windows
First distinguish failed discovery from failed access. If a known IP works manually, investigate multicast scope, adapter choice and isolation before changing credentials.
↗AeoCam / Knowledge center
Find a fix
Separate credentials, transport, decoding and storage problems before changing settings.
24 / 24
No matching guide. Try a camera brand or a shorter phrase.
Troubleshooting
RTSP 401 Unauthorized: check the account
A persistent 401 points to authentication, but an initial challenge can be normal. Verify the local protocol account, encoded credentials and lockout state before repeated retries.
↗Troubleshooting
RTSP 403 Forbidden: inspect access permissions
A 403 indicates the request was refused, not necessarily that the password is mistyped. Check account privileges and device access policies for that stream.
↗Troubleshooting
RTSP 404: verify the stream path and channel
A reachable camera can still reject an unknown stream path. Compare the exact product family, channel numbering and profile before changing network settings.
↗Troubleshooting
Camera connection timed out: narrow down the path
A timeout can happen before authentication starts. Confirm the current address, route and configured port, then compare a known local source on the same computer.
↗Troubleshooting
Connection refused: check the camera service
Connection refused often means the target is reachable but the selected service is not listening. Verify protocol enablement and the actual service port rather than changing passwords first.
↗Troubleshooting
Connected but the camera image is black
A connected session does not prove successful decoding. Verify the selected profile, a simpler documented stream and resource use before blaming the camera’s network address.
↗Troubleshooting
Camera image freezes while the app stays open
Check whether new frames stop arriving or only one view stops updating. Compare stream load, competing sessions and a wired path using the same camera profile.
↗Troubleshooting
Reduce camera live-view delay methodically
Measure visible lag before changing transport or encoding. A lower bitrate helps only if it preserves necessary motion detail and the source itself is current.
↗Troubleshooting
Why camera delay grows over time
Growing delay suggests a pipeline falling behind rather than a fixed network round trip. Record how lag changes with camera count, transport and decode load.
↗Troubleshooting
Green or corrupted camera frames
Corruption can involve packet loss, encoding or decoding. Compare transport and a lower-complexity profile independently, keeping a record of which change removes the artifacts.
↗Troubleshooting
Camera disconnects at regular intervals
Compare disconnect times with camera power, address renewal and session limits. Regular timing is useful evidence; it does not by itself identify an app reconnect defect.
↗Troubleshooting
Video works but camera audio is silent
First confirm the source profile carries audio. Distinguish missing audio, unsupported format and Windows output routing before changing camera network settings.
↗Troubleshooting
Video works but PTZ control does not
Streaming and movement use different capabilities and permissions. Check the ONVIF endpoint, profile association and control account instead of replacing the working video URL.
↗Troubleshooting
Recording appears active but no file is found
Verify the actual destination and completed recording state. A visible indicator or event entry does not prove a file was written and finalized.
↗Troubleshooting
Recording stops when the disk fills up
Confirm which volume is full and whether the installed build has a verified cleanup policy. Preserve needed clips before deleting disposable footage or changing retention.
↗Troubleshooting
Events exist but no Windows notification appears
Detection, event storage and notification presentation are separate checks. Confirm which notification controls exist in the installed build before concluding that detection failed.
↗Troubleshooting
Too many motion events: reduce irrelevant triggers
Review the triggering scene before lowering sensitivity globally. Reflections, trees and lighting changes may be better addressed by a narrower region and representative retesting.
↗Troubleshooting
A history entry exists but its clip will not play
Check that the linked file still exists on the expected volume and was finalized. Metadata can remain after a disk is disconnected or a file is removed.
↗Troubleshooting
Camera stopped working after an IP address change
Find the device again using its MAC address, then update the saved endpoint. Fix the address assignment rather than repeatedly editing account credentials.
↗Troubleshooting
Camera works locally but not over a VPN
A local success narrows the camera-side question. Check VPN routes, access rules and discovery assumptions before changing a working local account or stream path.
↗Troubleshooting
The stream shows the wrong camera or lens
A correct login can still select the wrong NVR channel or lens. Match the physical scene to the manufacturer’s channel mapping, including zero-based numbering where documented.
↗Troubleshooting
Microsoft Store installation does not finish
Use Microsoft’s Store troubleshooting steps before downloading an installer from an unrelated website. Separate Store delivery errors from later camera connection problems.
↗Troubleshooting
Camera viewing fails after Windows wakes
Check the restored network route and camera session after wake. Compare a clean reconnect with the pre-sleep state before changing the camera’s permanent configuration.
↗