You ran the cable, plugged the camera into the NVR, and… nothing. A black box where the video feed should be, or a “Video Loss” message staring back at you. Before you assume the camera is dead and start a return, work through these seven fixes in order. Nine times out of ten the problem is power, the cable, or an IP address mismatch – not a broken camera.
This guide is written for homeowners running their own system, so there’s no assumption you know networking jargon. We’ll explain each step as we go.
First, Confirm the Camera Actually Has Power
Before touching any settings, find out whether the camera is even turning on. A PoE (Power over Ethernet) camera gets both its power and its data through the single Ethernet cable, so if power isn’t getting through, the camera is simply off – and an off camera will never show up on your NVR.
Here’s the trick installers use: go to the camera and cover the lens completely with your hand or a cardboard box to simulate total darkness. After about 5 to 10 seconds, you should hear a faint click and see a soft red glow from the infrared LEDs as the camera switches to night mode.
If you get the click and the glow, the camera has power – skip ahead to the cable and IP fixes. If you get nothing, the problem is power delivery, and the next two fixes are where you’ll find your answer.
Fix 1: Swap the Cable and the Port
This is the single most common culprit, so do it first. Roughly nine out of ten PoE failures trace back to a bad cable termination or moisture that’s crept into the RJ45 connector at the end of the cable.
Take the camera down and bring it to the NVR. Using a short, factory-made patch cable – ideally the one that came in the box – plug the camera directly into the NVR. If the camera springs to life on a three-foot cable but stayed dark on the long run to its mounting spot, your long cable is the problem. It’s either damaged, crimped incorrectly, or pushed past the maximum distance (PoE tops out around 328 feet per run).
While you’re at it, plug into a different port on the NVR to rule out one dead port.
Fix 2: Check Your NVR’s Power Budget
Every NVR can only supply so much total power across all its ports – this is called the PoE budget. Cameras with spotlights, sirens, or pan-tilt-zoom motors draw a lot, and it’s easy to add a few power-hungry cameras and quietly exceed what your recorder can deliver. The newest camera you add is usually the one that goes dark.
To test it, unplug every other camera and leave only the problem camera connected. If it suddenly comes online by itself, your NVR’s power supply is stretched too thin for the full set. The fix is either swapping in lower-draw cameras or moving some cameras onto a separate PoE switch with its own power supply.
A PoE switch is a small box that powers and connects multiple cameras on its own, taking the load off your NVR. It’s one of the most useful upgrades for a growing system, and we’ll cover how to choose one in a dedicated guide.
Fix 3: The IP Address Conflict Nobody Warns You About
This is the one most people miss, and it’s sneaky. If you powered your cameras on while they were plugged into a regular network switch or router before connecting them to the NVR, two or more cameras may have grabbed the same default IP address. To the NVR, that looks like one camera flickering in and out – or several cameras refusing to appear at all.
Every camera needs its own unique IP address inside the same range as the NVR. The cleanest fix is to plug cameras into the NVR’s built-in PoE ports one at a time and let the NVR assign each one an address before adding the next. Most NVRs do this automatically when the camera is connected directly rather than through an outside switch.
If you’ve already created the conflict, reset the affected cameras to factory settings (there’s a small reset button – check your manual for how long to hold it), then re-add them one by one.
Fix 4: Don’t Delete and Re-Add Channels to “Fix” It
When a camera misbehaves, the instinct is to delete its channel and add it back fresh. Resist that urge. On many NVRs, deleting and re-adding cameras in the device registration menu causes new problems – duplicated channels or cameras that constantly drop offline – because the recorder had already bound that camera to a specific physical port.
If you need to reorganize which camera shows on which channel, the reliable method is physical: label each cable, then plug them into the back of the NVR in the order you want. Let the hardware do the mapping instead of fighting it in the menu.
Fix 5: Match the Subnet (When Using Wi-Fi or an External Switch)
If your camera connects over Wi-Fi or through a separate network switch rather than the NVR’s own ports, the two devices have to be on the same subnet – basically, the same neighborhood of IP addresses – to find each other. A mismatch here produces “connection failed” or “incorrect username or password” errors even when everything is physically plugged in correctly.
Restart your router, confirm both devices are on the same network, and temporarily disable any firewall to see if it’s blocking the connection. If the camera appears the moment the firewall is off, you’ve found your answer and can add an exception rather than leaving it off.
Fix 6: Update the Firmware on Both Devices
A camera and an NVR running mismatched firmware versions sometimes simply can’t talk to each other, even from the same brand. Manufacturers push updates specifically to fix these compatibility gaps. Check for firmware updates for both the NVR and the camera, apply them, then try adding the camera again. This is quick and worth doing before you conclude anything is broken.
Fix 7: Confirm the Password and Protocol
Newer cameras require you to set a password the first time they’re activated, and the NVR needs that exact password to pull the feed. If you’re seeing a username or password error on a camera you know is powered and connected, re-enter the credentials in the NVR’s camera settings. While you’re there, make sure the connection protocol matches – most systems default to a plug-and-play mode, but mixing brands occasionally means you need to select ONVIF, the universal standard that lets cameras and recorders from different makers work together.
Still Nothing? Here’s How to Know It’s the Camera
Work through all seven fixes and you’ve eliminated power, cabling, IP conflicts, subnet mismatches, firmware, and credentials. If a camera has confirmed power (you got the click and the IR glow), works on a short cable plugged straight into the NVR, has a unique IP, and still won’t produce an image – at that point it’s reasonable to treat the camera itself as faulty and pursue a warranty replacement.
The good news: by ruling everything else out first, you can describe exactly what you tested when you contact support, which gets you a replacement far faster than “it doesn’t work.”
A Quick Note on Building a System That Just Works
Most of these headaches come down to two things: marginal cabling and an underpowered or mismatched setup. If you’re still piecing your system together, choosing the right NVR and properly rated cable up front prevents the majority of the problems above.
Was this fix list helpful? The most common solution by far is Fix 1 (cable) or Fix 3 (IP conflict) – if you found yours, you just saved yourself a return and a week of waiting on a replacement.