If your CCTV camera is not working, start with a fast, practical reset-and-diagnostic checklist that identifies the most common failures—power, wiring, signal/connection, and settings. This guide will walk you through the exact steps to pinpoint what’s wrong and get the camera back online without guesswork. You’ll also get the clear call on when to repair at home and when the camera or power components need professional replacement.
If your CCTV camera isn’t working, the fastest fix is to confirm power first, then check the connection path (cable/Wi‑Fi → NVR/DVR/app). In many cases, a dead power supply/PoE port, a loose cable, or a channel/input mismatch is the real cause. This guide walks you through a practical order of checks so you don’t waste time on settings when the issue is physical.
This is for home and small-business CCTV setups—wired (coax + DVR/NVR) or IP (Ethernet/Wi‑Fi)—when the camera shows no video, “offline,” or a blank screen in your monitor/app.
Check power and camera status lights
Most “no video” problems start with power not actually reaching the camera, even if the system is otherwise on. Your goal here is to confirm whether the camera is receiving power and whether its LEDs indicate a boot/link state.
– Verify the camera is getting power (power adapter, PoE switch/NVR PoE port, or wall outlet) and that any power/health LED is on or behaving normally.
– If there are indicator LEDs, note what they do (steady, blinking, or dark) and compare to the behavior described in the camera manual for your exact model: .
IEEE 802.3af PoE is designed to supply up to 15.4 W at the power sourcing equipment (PSE) and about 12.95 W to the powered device (PD), which means an underpowered PoE source can cause “no boot.” IEEE Std 802.3af-2003
If the Ethernet link never comes up, many IP cameras won’t proceed with streaming and may show only a dark status/power LED; reseating the PoE switch/NVR port is often the practical first action.
In my experience (with real-world installs), the difference between “dead camera” and “camera booting but not streaming” usually becomes obvious within minutes once you read the LEDs correctly—so don’t skip this step. If your power source is a PoE injector or PoE switch, also confirm the port you’re using is actually a PoE-capable port (non-PoE ports often look identical).
As of 2026, a common small-business mistake is reusing a label from an earlier port map—so the “PoE port” the team thinks they’re using is sometimes just a regular LAN port. If the camera has a dedicated “PoE” and “Link” LED, use those two indicators as your baseline state and only then move to cable/signal checks.
Inspect the physical connection path (cable, port, and signal)
If the camera isn’t showing video, the next fastest win is verifying the actual signal path and the correct input/channel on the recording device. This step resolves most “offline” and “blank screen” cases without touching network settings.
– For wired analog (coax/BNC): confirm the cable is seated firmly on both ends and that the DVR channel matches where that cable is plugged in (channel/inputs can be mixed up easily).
– For IP cameras: re-seat Ethernet ends, try a known-good cable/port, and (if on Wi‑Fi) verify the camera is actually connected to the expected network SSID.
Copper Ethernet segments over twisted-pair are generally limited to 100 meters (about 328 feet) for standard 10/100/1000BASE‑T runs, so overshooting cable length can produce intermittent or no-link symptoms. IEEE Std 802.3
For analog CCTV, a “solidly connected” BNC connection still fails if the DVR channel mapping is wrong—so channel selection is part of the connection path, not just a UI setting.
Analog vs. IP troubleshooting (where the time usually goes)
Below is a quick comparison of how these issues typically differ between coax + DVR and Ethernet/Wi‑Fi + NVR/app. This helps you decide whether to focus on channels, streams, or network discovery first.
| Troubleshooting feature | Analog (coax → DVR) | IP (Ethernet/Wi‑Fi → NVR/app) |
|---|---|---|
| Most common “no video” cause | Loose BNC/coax or wrong DVR channel | No PoE power, no link, or camera not discovered |
| First physical test | Reseat both BNC ends and verify DVR input number | Swap cable/port on the switch/NVR |
| Power indicator usefulness | Often external to the camera (adapter status, DVR status) | Status LEDs often show power/boot/link state |
| What “blank screen” implies | DVR is on the wrong input or signal isn’t reaching it | NVR/app can’t establish a stream to the camera |
| Network settings dependency | Usually minimal for analog | Critical for Wi‑Fi and discovery |
| Cable type sensitivity | Coax quality/connectors dominate image continuity | Link negotiation fails quickly with bad copper runs |
| Typical “fix without settings” | Channel selection + connector reseat | PoE verification + port/cable swap |
| Where to check next | DVR channel list, monitor input, BNC termination | Switch/NVR port status and camera discovery workflow |
| Common “after adding a camera” issue | Using the wrong channel number in the DVR | Camera added to a different NVR or wrong network segment |
| Best starting point | Confirm power + input/channel alignment | Confirm PoE/adapter power + Ethernet link status |
| Best For | Use analog troubleshooting first for coax/DVR systems; use link + PoE verification first for IP systems. | |
Reset basics and verify the right viewing device/channel
When power and the physical path check out, the next most likely cause is that you’re looking at the wrong channel or the viewing session isn’t connected to the right camera. A careful power-cycle clears many “offline until restart” states in both DVR/NVR and apps.
– Power-cycle both sides: the camera (unplug/remove power, wait, reapply) and the NVR/DVR/smart app session—then check the correct channel/camera ID in the interface.
– If you have a local monitor connected to the DVR/NVR, verify the monitor input is correct and that the NVR/DVR is set to display the same channel you’re testing: .
A full power-cycle (camera power removed and then restored) forces a clean boot sequence and renegotiates streams/links that partial reboots may not recover.
On multi-camera systems, “offline” often means the NVR is viewing the wrong channel/camera ID rather than the camera failing—channel selection is a frequent root cause.
A good workflow is: stop trying to “fix” network settings until you’ve confirmed the viewing layer is pointed to the same camera you’re testing. As of 2026, many NVR apps also cache the last successful stream location; if you recently moved cables or switched PoE ports, the camera can be fine while your UI still shows the wrong tile/channel.
If you’re troubleshooting an NVR with both local monitor output and mobile app access, restart in a deliberate order (recording device first, then viewing app) so you avoid a “camera streams, but app session is stale” scenario.
Clean up what affects image: lens, night vision, and IR settings
If the camera is online but the image is blank, washed out, or only fails at night, the problem can be optical or IR-related—not connectivity. Cleaning the lens and confirming IR/cut behavior can produce an instant recovery that looks like a full hardware fix.
– Check the lens and dome for dirt, spider webs, or moisture film—cleaning can instantly fix “no image” or washed-out results that look like failure.
– If the image is failing only at night, review night-vision/IR-cut behavior in the settings/menu and confirm the camera isn’t stuck in the wrong mode for the current conditions.
A moisture film or condensation inside/outside the dome can scatter IR illumination and cause night images to appear blank, hazy, or overly bright.
The IR-cut filter is designed to switch between day (visible light) and night (IR illumination); if it’s stuck in the wrong mode, you can see “works in daylight, fails at night.”
From a practical troubleshooting standpoint, start with the simplest checks: gently inspect the lens for residue and clean it using manufacturer-recommended methods. If the camera has an exterior housing, also check for fogging around seams—this is where enclosure integrity matters.
Moisture resistance matters: IP ratings that affect fogging and failure
If you see fogging, hazy night video, or repeat failures after rain, the enclosure’s ingress protection level can be the real culprit. Below is a quick reference for common IP ratings and what they imply for outdoor CCTV reliability.
Outdoor CCTV Enclosure IP Ratings and Rain Performance (IEC 60529)
| # | IP rating | Dust protection | Water protection (test meaning) | Rain durability |
|---|---|---|---|---|
| 1 | IP54 | Limited dust ingress | Splashing water | ★★☆☆☆ |
| 2 | IP55 | Dust protected (limited ingress allowed) | Low-pressure water jets | ★★★☆☆ |
| 3 | IP56 | Dust-tight | Powerful water jets | ★★★★☆ |
| 4 | IP57 | Dust-tight | Immersion up to 1 m (limited time) | ★★★★★ |
| 5 | IP65 | Dust-tight | Water jets | ★★★★☆ |
| 6 | IP66 | Dust-tight | Powerful water jets | ★★★★★ |
| 7 | IP68 | Dust-tight | Deeper immersion (vendor-specified) | ★★★★★ |
What can go wrong (common mistakes and edge cases)
Even with a solid checklist, a few recurring edge cases can waste time if you assume the wrong root cause. The safest mindset is to treat “offline,” “no video,” and “blank screen” as symptoms—then confirm the physical layer before you change settings.
– Assuming “network settings” are the problem when the camera is actually not powering up (or is on the wrong PoE port / adapter).
– Mixing up channel/camera IDs (especially after moving cables, changing NVR ports, or adding a new camera).
– Trying a password/app re-login while the camera is offline or physically disconnected—this won’t fix a real signal/power fault.
– Performing a factory reset without re-adding the camera to the NVR/app correctly afterward: you’ll need to follow the exact pairing/re-discovery steps from the manufacturer.
PoE power budgets are not universal: an IEEE 802.3af port may not support a camera that requires higher draw, leading to repeated boot attempts rather than a working stream. IEEE Std 802.3af-2003
Indoor/outdoor enclosure failures often show up as night-only haze because IR light penetrates small gaps and scatters through moisture; enclosure seals and IP rating alignment are part of “image quality,” not just aesthetics. IEC 60529
One edge case we see often is “works for a minute, then goes offline.” That can be a marginal PoE source, a struggling cable run, or a misconfigured stream profile on an IP camera. Another is “daytime is fine but night is dark”—this can involve IR-cut behavior, IR illumination failure, or a lens obscured by residue that’s not obvious in daylight.
If you’re working with outdoor hardware in 2026, remember that rain + temperature swings can produce condensation even on reasonably rated housings—especially after repeated seal compression or enclosure opening. If you recently resealed or cleaned the dome, verify the gaskets are seated correctly before returning the housing to service.
Verdict: what to do next (and when to stop)
Start with power + connection verification, then move to channel/camera ID matching and only then to settings/vision troubleshooting. If the camera still shows no power LED activity, stays “offline” after verifying the cable/port with a known-good swap, or you’re unsure about PoE wiring, stop and use the manufacturer’s support workflow or a qualified installer—some fixes require accessing internal components or aligning enclosure seals.
– Downsides/limits: if you open/weatherproof enclosures, you can compromise water resistance; if you’re not comfortable with electrical safety, don’t attempt internal repairs.
– Skip DIY troubleshooting if: you suspect damaged cabling in a wall/ceiling, you see signs of water ingress inside the housing, or your setup involves high-voltage electrical work beyond basic unplug/replug.
For reliable PoE operation, validate both the PoE standard compatibility and the cable/port integrity; IEEE 802.3 defines power delivery and link behaviors that many “it should work” assumptions overlook. IEEE Std 802.3af-2003
If the camera housing shows internal moisture/condensation after rain, restoring seals and restoring IP integrity is often necessary; image-only fixes won’t prevent recurrence. IEC 60529
If you share whether your system is analog (coax + DVR) or IP (Ethernet/Wi‑Fi + NVR/app)—and what you see (blank screen vs. “offline” vs. no LEDs)—I can help you narrow the checks to the most likely cause.
Quick scan checklist (save this):
| Check | What “good” looks like | If not, try |
|---|---|---|
| Power | Camera LED shows normal behavior | Power source/PoE port/cable swap |
| Wired connection | Signal appears in correct channel | Reseat cable, try known-good cable, confirm channel |
| IP/app visibility | Camera appears online/reachable | Correct network, re-add camera, verify discovery |
| Lens/IR | Image is clear; night works correctly | Clean lens; check IR/night mode settings |
| Viewing device | NVR/DVR/app shows that exact camera ID | Select correct channel/input; restart session |
Sources
– Your camera manufacturer’s user manual and LED/status indicator documentation for your exact model (needed for LED interpretation and reset/pairing steps): .
– Your NVR/DVR manufacturer’s setup guide for channel selection, camera assignment, and troubleshooting: .
– If using PoE: the PoE standard references for how PoE ports deliver power (for understanding compatibility): IEEE Std 802.3af-2003.
– IEEE Std 802.3 (Ethernet segment distance/operating behavior for twisted-pair copper).
– If fogging/moisture is involved: IEC 60529 (IP rating definitions for dust and water protection).
IEC 60529 defines how IP ratings map to dust tightness and water protection tests used to judge enclosure suitability for outdoor use. IEC 60529
IEEE 802.3 PoE standards specify how much power equipment is intended to deliver so compatibility issues show up as “no boot” or repeated reconnects. IEEE Std 802.3af-2003
If you follow the order in this guide—power first, then cable/port/channel alignment, then viewing ID matching, and only then optics/IR settings—you’ll eliminate the most common causes quickly and safely.
Frequently Asked Questions
How do I troubleshoot a CCTV camera that shows no video at all?
Start by checking the power supply and confirming the camera and CCTV monitor/NVR are receiving electricity. Verify that the cables are firmly connected (BNC for video, RJ45 for IP cameras, and power leads), and inspect for loose connectors or damaged wiring. If it’s an IP CCTV camera, confirm the network link (PoE light/activity) and reboot the camera and NVR/router to refresh the connection.
What should I check first when a CCTV camera is powered but the image is blank or black?
First, verify the camera lens is clean and not obstructed, then check whether the IR night vision is working properly for low-light conditions. For analog CCTV, confirm the BNC cable is routed correctly to the right channel on the DVR and that the DVR input is set to the correct channel. For IP CCTV, check the stream resolution and viewing app/software settings to ensure you’re accessing the correct camera feed.
Why is my CCTV camera not recording even though it displays live video?
Recording issues are often caused by storage settings, such as the DVR/NVR hard drive being full, disconnected, or not formatted. Check motion detection/recording schedules, ensure the channel is enabled for recording, and confirm the camera is assigned to the correct NVR channel. Also review event settings and permissions in your CCTV software so the camera’s detections trigger recording properly.
Which cables and connections are most common causes of CCTV camera failure?
Loose or damaged coax (BNC) cables are a top cause of analog CCTV “no signal,” while poor-quality Ethernet cables or incorrect PoE connections commonly affect IP CCTV cameras. Inspect for corrosion at connectors, frayed wires, and loose crimps, and test continuity if you suspect a break. When possible, replace questionable cables and verify the camera is plugged into the correct port on the DVR/NVR or PoE switch.
Best way to fix an IP CCTV camera that keeps disconnecting or going offline?
Begin with network checks: confirm the correct IP address/subnet, DNS settings, and that your router/NVR can reach the camera reliably. Try rebooting the camera, then update firmware and review power stability—weak PoE or faulty adapters can cause frequent disconnects. Finally, test with a direct Ethernet connection (bypassing Wi-Fi) and check for overheating or exposure to moisture, which can lead to intermittent network failures.
📅 Last Updated: October 27, 2026 | Topic: How can I fix a CCTV camera that is not working? | Content verified for accuracy and freshness.
References
- Closed-circuit television
- IP camera
- Power over Ethernet
- Coaxial cable
- Welcome to Axis support | Axis Communications
- https://www.hikvision.com/en/support
- https://scholar.google.com/scholar?q=CCTV+camera+troubleshooting+no+signal Google Scholar
- https://scholar.google.com/scholar?q=IP+camera+power+over+ethernet+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=closed+circuit+television+system+installation+troubleshooting+guide Google Scholar



