Camera setup

How to Connect Reolink Cameras to LightNVR

Enable the camera's RTSP service, verify the main and fluent streams locally, then connect both feeds to LightNVR without exposing the camera to the public internet.

9 min read Difficulty: Beginner

1. Before you start

This guide assumes the camera is already powered, activated, and visible on your local network. Complete the RTSP test from a computer on that same network before involving a VPN or cloud recorder. That separates a camera configuration problem from a routing problem.

You will need:

The camera’s local IP address
A camera-local username and password with live-view permission
A computer with VLC or ffprobe for the local test
Network access from LightNVR to the camera, directly or through a private tunnel

Check the model first. RTSP support varies by model. Battery-powered cameras and some cameras bundled for specific Reolink NVR kits may not expose a standalone RTSP service. Check Reolink's compatibility list for your exact model before troubleshooting the network.

2. Prepare the Reolink camera

Find and reserve the camera IP: Use the Reolink app/client or your router's DHCP lease list, then create a DHCP reservation so the address does not change after a reboot.
Enable the server ports: In the Reolink client or camera web interface, open Network settings, find Advanced or Server Settings, and enable RTSP. The default RTSP port is 554.
Confirm the camera account: Use a camera-local username and password. These are the credentials used to sign into the camera itself, not a LightNVR account.

A DHCP reservation is enough; the camera does not need a manually configured static IP. The goal is simply to keep its address from changing underneath the recorder.

3. Build the main and sub-stream URLs

Replace the placeholders with the camera account and reserved local IP address.

Use	RTSP URL
Main recording stream	`rtsp://username:password@CAMERA_IP:554/Preview_01_main`
Lower-bandwidth live stream	`rtsp://username:password@CAMERA_IP:554/Preview_01_sub`

 Preview_01_main is Reolink's clear/main stream; Preview_01_sub is the lower-bandwidth fluent stream. Cameras connected through a Reolink NVR or Home Hub can use different channel numbers, so use Reolink's channel-specific documentation for those topologies.
  🔑 
If a username or password contains reserved URL characters such as @,
:, /, ?, or #, percent-encode that value
        before embedding it in the URL. Do not weaken the camera password just to make the URL easier to type.

4. Test the feed locally

Quick visual test with VLC

Connect the test computer to the same network as the camera.
In VLC, choose Media → Open Network Stream.
Paste the main-stream URL and select Play.
Repeat with the sub-stream URL and confirm it is the lower-resolution feed.

Inspect the stream with ffprobe

This reports the codec, dimensions, and frame rate without creating a recording:

ffprobe -v error -rtsp_transport tcp \
  -show_entries stream=codec_name,width,height,r_frame_rate \
  -of default=noprint_wrappers=1 \
  "rtsp://username:password@CAMERA_IP:554/Preview_01_main"

Do not move on until at least the main URL works locally. If it fails, use the RTSP troubleshooting checklist to identify authentication, path, port, and codec failures in that order.

5. Add the camera to LightNVR

Confirm the LightNVR host can route to the camera IP. A cloud instance should use a WireGuard tunnel; do not forward RTSP port 554 from the public internet.
Open the LightNVR interface and select Streams in the main navigation.
Select Add Stream.
Under Basic Settings, enter a short name such as front_door.
Paste the main URL into Stream URL.
Paste the lower-bandwidth URL into Sub Stream URL.
Optionally enter the camera’s web address in Camera Admin URL.
Select Test Connection. Save with Add Stream only after the test succeeds.

Verify both outcomes: open Live to see the camera now, then open Recordings after a recording segment closes to confirm footage is being retained.

6. Tune recording and live view

Once the basic connection is stable, tune one setting at a time:

Start with H.264 while proving the connection. Move to H.265 only after recording and browser playback both work.
Use the main stream for recording and the fluent/sub stream for multi-camera live view.
Disable “Interframe Space” or smart-codec options temporarily if a third-party client reports irregular keyframes.
Budget using the camera’s configured bitrate, not resolution alone. A 4 Mbps stream transfers about 43 GB per day before retention overhead.
After every codec or profile change, rerun Test Connection and check a newly created recording.

7. Troubleshooting

VLC says connection refused

Re-open Server Settings and verify RTSP is enabled.
Confirm the URL uses the camera IP, not a Reolink UID or cloud identifier.
Check whether your exact model supports RTSP; many battery models do not.

The sub stream works but the main stream does not

Switch the clear/main stream to H.264 for the first test.
Reduce the clear-stream resolution or bitrate to rule out decoder and bandwidth limits.
Retest Preview_01_main in VLC before changing anything in LightNVR.

It works in VLC locally but not from LightNVR Cloud

Confirm the WireGuard tunnel shows a recent handshake.
Confirm the routed camera subnet contains the camera IP.
Test TCP port 554 from the LightNVR side; a successful ping does not prove RTSP is reachable.
Open System → System Logs, reproduce the failed connection, and inspect the newest warning or error.

8. Keep the connection secure

Use a dedicated camera user with live-view permission instead of the administrator account.
Keep the camera on an isolated camera or IoT VLAN when practical.
Route RTSP through the LAN or WireGuard; never expose port 554 directly to the public internet.
Keep camera firmware current and remove unused accounts and services.
Remember that credentials embedded in an RTSP URL are sensitive. Do not paste a real URL into public issues or screenshots.

Vendor reference: Reolink: live view cameras via VLC. Menu names can move between firmware versions, but the linked vendor documentation is the source of truth for the stream path.

Related guides

📹