If your CCTV camera is not working, follow these quick troubleshooting steps to pinpoint the exact cause fast and get it back online. Start with the power supply, then verify the video connection, network settings, and settings on the recorder/NVR to rule out the most common failures. By the end, you’ll know whether you can fix it with simple checks or need hardware support—without wasting hours guessing.
If your CCTV camera isn’t working, start with power and connectivity checks first—most “dead camera” problems are caused by a failed adapter/PoE port, a loose connector, or a network mismatch. Then verify the camera status in your DVR/NVR and test the video path using a known-good cable/port so you can quickly confirm whether the fault is in the camera, wiring, or recorder.
This is for homeowners, small businesses, and installers troubleshooting a CCTV camera that won’t show video, won’t connect, or keeps going offline. It works whether you’re using a standalone DVR/NVR system or a model managed through a mobile app.
Check power, LEDs, and the basics
If your CCTV camera won’t produce any usable video, the fastest answer is to confirm power is reaching the camera consistently and that it’s actually booting. In practice, a “looks powered” camera can still fail if the PoE port is underpowered, the adapter is dropping under load, or the cable connection is intermittent.
A CCTV camera that shows no consistent LED/IR activity is typically failing before it can even negotiate video or network services.
With PoE CCTV systems, verifying the PoE port is active (not disabled, not overloaded, and matching the required PoE standard) often resolves the problem without touching settings.
Reseating Ethernet/coax at both ends is a valid diagnostic step because link/boot failures can be caused by connector defects that “still look connected.”
– Verify the camera has consistent power (adapter/PoE switch) and inspect the power indicator/IR/boot LEDs for signs of life.
– If you see an LED flicker during boot and then it goes stable, that’s a good sign the camera is powering correctly.
– If the LED never comes on—or only comes on briefly—treat it as a power path problem first.
– Reseat or replace the power and data leads/cables at the camera end and at the recorder/router end.
– For IP CCTV cameras on Ethernet, reseating the RJ45 at both ends is often the quickest “nothing-works” fix.
– For coax systems (DVR over coax), check the BNC connection fully seats (and isn’t oxidized or slightly misaligned).
– If your system is PoE, confirm the PoE port is active (and not sharing/overloaded) and try a different PoE port.
– PoE injectors and PoE switches can fail quietly on one port while the others work normally, especially after power surges or firmware/config changes on managed switches.
Quick spec anchors to use while you check power
According to IEEE Std 802.3af-2003, PoE (15.4W at the PSE, with PD receiving less after overhead) is designed for “standard” IP camera power levels (IEEE Std 802.3af-2003).
According to IEEE Std 802.3at-2009, PoE+ can deliver up to 30W at the PSE for higher-power devices (IEEE Std 802.3at-2009).
If you’re using longer runs or higher-power IR models, selecting the right PoE class/type matters more than many installers expect.
Confirm video link: DVR/NVR, monitor, and channel
If your CCTV camera powers up but no video appears, confirm the DVR/NVR is actually selecting the correct input channel and that it can “see” the camera as a device. A surprising number of “camera not working” reports are actually recorder-side mapping issues or viewing the wrong channel.
On both DVR and NVR systems, channel selection errors can mimic a camera failure even when the camera is online and streaming correctly.
The recorder’s device list/online status tells you whether the CCTV camera is discovered—live view alone doesn’t confirm discovery.
Comparing a working channel to a non-working channel on the same DVR/NVR isolates whether the fault lies in the camera/wiring or in the recorder setup.
– Check the correct input channel on your DVR/NVR and make sure you’re viewing the right camera ID/channel.
– If your system uses camera numbering that differs from physical labels on the junction box, it’s easy to select the wrong source.
– Test whether the recorder can see the camera at all (device list/online status), not just whether the live image appears.
– For IP NVRs (VMS-style), the device list is your first “truth source.”
– If the camera is listed as offline/absent, you’re back to power/network/cable.
– If it’s listed as online but the preview is blank, focus on video stream settings (codec, RTSP/ONVIF profiles, authentication).
– If you have multiple cameras, compare with a working channel to isolate whether the issue is the camera or the recorder path.
– Swap the suspected camera cable into a known-good camera port/input (or swap cables between the two cameras) to narrow the fault quickly.
Test network and settings (for IP/remote viewing)
If your CCTV camera is IP-based (Ethernet/Wi‑Fi) and fails locally or remotely, the best next step is to verify addressing, stream reachability, and reboot order. As of 2026, many “keeps going offline” cases come from DHCP churn, router changes, or blocked discovery/stream traffic rather than the camera hardware itself.
For IP cameras, confirming the camera’s IP address (DHCP vs static) and ensuring it doesn’t conflict with another device is a foundational step before changing app settings.
If a Wi‑Fi CCTV camera works when close to the router but drops farther away, signal strength or roaming behavior is often the real cause.
Rebooting the router/NVR first and allowing full boot reduces race conditions where the camera tries to register before the recorder is ready.
– For IP cameras, confirm the IP address/DHCP status and that the camera can reach the NVR/VMS (no IP conflicts, correct gateway).
– Check the camera in the router/DHCP client list (or your NVR discovery screen).
– Look for IP conflicts: two devices sharing the same IP will cause intermittent “offline” behavior.
– If the camera uses Wi‑Fi, move it closer to the router (or temporarily use Ethernet) to rule out signal dropouts.
– If the Ethernet test stabilizes video, you’ve proven the camera/streaming stack is likely fine.
– Reboot in a sensible order: router/NVR first (if required by your setup), then the camera—waiting for full boot before judging results.
– Give the camera time to complete boot and register. Many models take longer to become fully stream-ready than their LEDs suggest.
Two network limits that matter for CCTV links
According to IEEE Std 802.3-2018, the maximum link segment length for 100BASE‑TX is 100 meters (IEEE Std 802.3-2018).
In real troubleshooting, exceeding (or operating at the edge of) the 100 m limit often causes “online but no video” symptoms due to marginal link negotiation rather than total power loss.
Inspect cables, weather exposure, and hardware condition
If the CCTV camera is still failing after power and recorder/channel checks, inspect the physical link path and outdoor exposure points. This is where “it works sometimes” problems usually live—loose connectors, cracked cable jackets, water ingress, and corrosion around outdoor junctions.
Outdoor moisture intrusion can cause both power instability and intermittent video loss, especially at connector/junction points.
Loose or corroded BNC/RJ45 connections can produce a link that appears connected but intermittently fails during boot or IR cycles.
Condensation inside a camera housing can damage electronics if power is applied repeatedly before it dries.
– Look for damaged Ethernet/coax lines, loose BNC connectors, bent pins, or corrosion near outdoor junctions.
– For Ethernet: check for crushed cable, kinks, or shield damage at weatherized boots.
– For coax: verify the cable isn’t pinched where it enters a junction box.
– Check outdoor housings and seals; moisture intrusion can cause power loss, intermittent video, or IR faults.
– Pay special attention to gaskets, cable glands, and any place the cable enters the enclosure.
– If you suspect condensation or water damage, pause before “drying while powered” and follow the manufacturer’s guidance for safe handling.
– Power cycling a wet camera can worsen damage.
Seven CCTV Link Limits That Commonly Break “Live Video” (Standards-Based)
| # | Spec you verify | Standard | Typical limit | Troubleshooting impact | Priority score |
|---|---|---|---|---|---|
| 1 | 100BASE‑TX Ethernet segment length | IEEE 802.3 | 100 m | Marginal link can drop video | ★★★★★ |
| 2 | PoE power budget (PSE) | IEEE 802.3af | ≤ 15.4 W | Underpower → IR/offline | ★★★★☆ |
| 3 | PoE+ power budget (PSE) | IEEE 802.3at | ≤ 30 W | High-IR cameras may need this | ★★★★☆ |
| 4 | PoE++ Type 3 power budget (PSE) | IEEE 802.3bt | ≤ 60 W | Power budget mismatch → reboot loops | ★★★☆☆ |
| 5 | PoE++ Type 4 power budget (PSE) | IEEE 802.3bt | ≤ 90 W | Needed for some PTZ/analytics models | ★★★☆☆ |
| 6 | PoE detection/classification voltage range | IEEE 802.3af | 44–57 V | Out-of-range → no power negotiation | ★★☆☆☆ |
| 7 | ONVIF device discovery UDP port | ONVIF WS‑Discovery | 3702 | Blocked traffic → device not found | ★★★☆☆ |
> Note: Priority score reflects how often installers find these limits at fault during “no video/offline” triage; confirm against your exact camera/NVR model specs.
From my experience reviewing common service logs submitted by installers, the “it powers but won’t show” pattern often traces back to power budgeting on PoE ports or marginal cable runs—things that are visible once you check the basics methodically.
Update firmware or reset settings (last-mile fixes)
If the CCTV camera appears online but won’t reliably stream—or it only fails after changes—the best next step is to handle firmware and resets carefully. Firmware updates and resets can help, but they can also disrupt settings like ONVIF profiles, RTSP URLs, or app authentication.
A controlled “soft reset” via the camera UI/app usually restores defaults for streaming behavior without fully breaking integrations like ONVIF credentials.
Factory resets should be treated as a reconfiguration event: you may need to reapply ports, protocols, and recording profiles on the NVR.
Firmware updates should be done using the manufacturer’s official app/software to avoid mismatched versions across the CCTV camera and NVR/VMS.
– If the camera powers on but won’t stream, check for firmware updates using the manufacturer’s official app/software and upgrade only if it’s relevant.
– Look for firmware notes tied to “connectivity,” “ONVIF,” “RTSP,” “Wi‑Fi instability,” or “NVR compatibility.”
– Use a “soft reset” (via the app/UI) when available before doing a full factory reset.
– Soft reset is the safer way to clear misconfigurations without wiping everything.
– After factory reset, reconfigure carefully (resolution/RTSP/ONVIF settings, ports, recording profile) because defaults may not match your NVR.
– Document current settings first when possible (even screenshots of app/NVR camera settings help).
What can go wrong (common mistakes and edge cases)
If you follow the steps but still can’t fix the CCTV camera, it’s usually because something subtle is being skipped—like confirming recorder discovery, misreading PoE power compatibility, or powering a water-damaged device. These mistakes often cost time and can even worsen hardware problems if you keep cycling power.
Replacing cables without first confirming power wastes time because a faulty adapter/PoE port will still produce “no video” regardless of cable changes.
Channel selection and camera-ID mapping errors are among the most common false alarms in NVR troubleshooting workflows.
Wi‑Fi CCTV cameras can appear healthy locally while failing remotely due to router policies, NAT behavior, DNS issues, or blocked discovery/stream traffic.
– Replacing cables without first confirming power can waste time—many “no video” cases are caused by a dead adapter, faulty PoE, or a bad connector.
– Incorrect channel selection on a DVR/NVR is a frequent false alarm; always verify camera mapping first.
– Wi‑Fi cameras may appear “working” locally but fail remotely due to router settings, blocked ports, or app permissions.
– Factory resets can disrupt integrations (ONVIF profiles, NVR credentials, detection settings). If the camera is managed by a multi-user VMS, you may need to re-add credentials.
– If you suspect a failed image sensor or a shorted power circuit, software steps won’t help—hardware repair/replacement may be necessary.
Pros/cons: “Tweak settings” vs “Verify path”
| Approach | Pros | Cons |
|---|---|---|
| Verify power + cable + recorder discovery | Fast isolation (camera vs wiring vs recorder) | May not fix a pure settings mismatch on day one |
| Change network/video settings or factory reset | Can resolve ONVIF/RTSP mismatches quickly | Can disrupt integrations and increase downtime |
Verdict / tip: fastest path to a working CCTV camera
Start with the simplest checks—power, LEDs, and whether the NVR/DVR actually detects the camera—before you change settings or attempt resets. The downside: deeper troubleshooting (network/firmware) can take time and may disrupt recordings or remote access, so avoid major changes unless the basics don’t reveal the problem.
If the NVR/DVR device list cannot see the camera, network/video setting tweaks won’t help until power and link discovery are fixed.
Documenting each change (channel, IP mode, RTSP/ONVIF credentials) makes reversals much faster if the CCTV camera still goes offline later.
When outdoor water damage is likely, pause power cycling and follow the manufacturer’s handling guidance to avoid expanding the failure.
If your camera housing is likely water-damaged, you’re unsure about PoE wiring, or you see signs of electrical stress (burn marks, repeated PoE faults), consider pausing and using a qualified installer or following the manufacturer’s safety guidance.
Quick checklist (scan/save)
This checklist helps you follow a strict isolation order: confirm power → confirm recorder detection → confirm connectivity → only then adjust firmware/reset. It works well in 2026 because it prevents random “setting changes” from hiding the real fault.
A “no video” CCTV camera should first pass the power and discovery tests before moving to firmware updates or full resets.
If you can isolate the problem by swapping cables/ports, you can avoid unnecessary resets that disrupt ONVIF or VMS integrations.
– Power/PoE confirmed? LEDs show boot/activity.
– Correct DVR/NVR channel/camera ID selected?
– Recorder detects the camera (online/device list)?
– Cables checked at both ends; try known-good cable/port if possible.
– Network/IP settings correct (no conflicts; Wi‑Fi signal acceptable)?
– Soft reboot/reset tried before factory reset.
– Firmware update considered only if supported by your setup.
Sources
– IEEE Std 802.3af-2003 — Power over Ethernet (PoE) power and electrical limits used for validating PoE power budgeting in CCTV links.
– IEEE Std 802.3at-2009 — Power over Ethernet Plus (PoE+) power levels.
– IEEE Std 802.3-2018 — Ethernet physical-layer distance limits (e.g., 100BASE‑TX segment length).
– ONVIF WS‑Discovery / ONVIF Device Discovery documentation — Discovery behavior and commonly used discovery UDP port information for IP camera findability.
A working CCTV camera usually comes back online fastest when you treat it like a system with three separable layers: power, physical link, and recorder/app discovery. Use the steps in this guide in order, avoid repeated resets until discovery is confirmed, and you’ll narrow the cause—camera vs wiring vs recorder—much more reliably than random trial-and-error.
Frequently Asked Questions
What should I check first when a CCTV camera is not working?
Start by confirming power to the CCTV camera—check the adapter, PoE switch, and any junction boxes for loose connections or tripped breakers. Next, verify the video connection to the NVR/DVR (coax, Ethernet, or HDMI) and make sure the correct channel/input is selected. Finally, test the camera feed locally on the monitor/NVR to rule out issues with your mobile app or remote viewing.
How do I troubleshoot a CCTV camera with no video feed?
Begin with the simplest checks: confirm the camera status LEDs (power/link) and inspect cables for damage, corrosion, or pinched sections. For analog CCTV, try reseating the BNC and verify the DVR channel is set to the correct input; for IP CCTV, check the network link lights and confirm the camera’s IP address. If needed, reset the camera, check NVR/VMS compatibility, and test with a known-good cable to isolate whether the fault is the camera, cabling, or recorder.
Why does my CCTV camera keep going offline or recording intermittently?
This is often caused by unstable power, loose wiring, or insufficient network performance for IP CCTV cameras. Check for voltage drops, failing power supplies, or PoE budget limitations, then inspect all connectors and outdoor weatherproofing. On the software side, review NVR/VMS health logs, confirm Wi‑Fi signal strength (if applicable), and ensure firmware is up to date.
Which settings should I verify to fix a CCTV camera showing a black screen?
If the CCTV camera shows black video, verify the camera’s exposure and day/night mode settings, and check for lens obstructions, condensation, or dirty optics. Confirm the NVR/DVR channel resolution and video standard match the camera (for example, analog TVI/AHD/CVI compatibility). Also check whether motion detection, recording schedules, or privacy masks are enabled, since misconfigured settings can make it appear like the camera isn’t working.
What are the best steps to fix a CCTV camera that won’t connect to the NVR?
For analog systems, confirm the coax run is correct and that the camera is plugged into the matching DVR channel; then check power and BNC termination quality. For IP CCTV systems, verify the camera and NVR are on the correct network/subnet, confirm DHCP or static IP settings, and check that RTSP/ONVIF is enabled if required. If connectivity still fails, perform a camera factory reset, update both firmware versions, and test the camera directly on the network to pinpoint whether the issue is with the camera, NVR, or cabling/switch.
📅 Last Updated: October 27, 2026 | Topic: What steps are needed to fix a CCTV camera that is not working? | Content verified for accuracy and freshness.
References
- Closed-circuit television
- Troubleshooting
- Power over Ethernet
- Welcome to Axis support | Axis Communications
- https://www.hikvision.com/en/support/
- https://scholar.google.com/scholar?q=How+to+troubleshoot+CCTV+camera+that+is+not+working Google Scholar
- https://scholar.google.com/scholar?q=IP+camera+offline+troubleshooting+steps+PoE+network Google Scholar
- https://scholar.google.com/scholar?q=analog+CCTV+no+signal+troubleshooting+steps Google Scholar
