Back to Lorex Guides
Lorex

Why Won't My Lorex Remote Viewing Work on My Phone?

Lorex GuideSecurity Cameras
medium difficulty 20 minutes 152 views 3 found helpful Where this fix applies: Global Updated
This guide applies to: Lorex Lorex NVR/DVR (All NVR and DVR Models)
At a glance — most common causes
  • NVR/system has no internet connection
  • Router blocking the connection (firewall/UPnP off)
  • P2P/cloud connectivity not enabled or UID not added
20 minutes13 solutions coveredmedium level

Expert Review & Technical Scope

DeviceLorex Lorex NVR/DVR
Model CoverageAll NVR and DVR Models
Fix Time20 minutes
DifficultyMedium
Required ToolsLevel, Clean microfiber cloth, Replacement batteries, Ethernet cable
Network / ProtocolWi-Fi / app-based troubleshooting context

Problem Description

You cannot view your Lorex cameras remotely on your phone when away from home. The Lorex Home app shows the system as offline or times out when trying to connect. Remote viewing requires the NVR to have an active internet connection and either Lorex cloud connectivity or port forwarding configured on your router.

Why This Happens in Real Homes

Remote viewing is where a lot of Lorex users get stuck, because it depends on the NVR reaching the internet and your phone being able to reach the NVR from outside. The first check is simple: the NVR itself must be connected to your router with a live internet connection - a system that records perfectly on local cameras but shows offline in the app almost always has no internet path. The modern, easy method is P2P (cloud) connectivity: enable it on the NVR and add the system to the Lorex Home app by its UID or QR code, which avoids router configuration entirely. This is the recommended path for most people.

When P2P isn't used or won't connect, the classic barriers are router and ISP related. Manual setups need port forwarding and DDNS configured on the router, and any setup can be blocked by a strict firewall (enabling UPnP or opening the required ports helps). Two ISP-side issues cause a lot of grief: double NAT (a modem and a router both doing NAT) and CGNAT (where your ISP doesn't give you a real public IP) both prevent inbound remote access - the fixes are bridging one device or asking the ISP for a public IP, though P2P usually sidesteps CGNAT. Also confirm your login is correct, that the NVR site has enough upload bandwidth for streaming, and that firmware and the app are current.

Symptoms

  • Can't view cameras remotely when away
  • Lorex Home app shows the system offline
  • App times out connecting
  • Works on home WiFi but not on cellular
  • Live view fails remotely but records locally
  • Remote view very slow/buffers
  • Notifications stop when away
  • App connected but no video

Recognize these? Here's what usually causes it.

Common Causes

  • NVR/system has no internet connection
  • Router blocking the connection (firewall/UPnP off)
  • P2P/cloud connectivity not enabled or UID not added
  • Port forwarding/DDNS not configured (manual setups)
  • Low upload bandwidth at the NVR site
  • Login/credentials wrong in the app
  • Double NAT or CGNAT blocking remote access
  • Firmware out of date

Most fixes happen in the first 3 steps.

Warning

Use strong password - NVR is accessible from internet.

Tools & Requirements

LevelClean microfiber clothReplacement batteriesEthernet cablePower adapter

Step-by-Step Solution

1

Check that the NVR is connected to the internet

The NVR must be connected to your router via Ethernet for remote viewing to work. On the NVR, go to Main Menu > Network > TCP/IP. Check that the NVR has an IP address, subnet mask, gateway, and DNS server configured (these are usually assigned automatically via DHCP). Test the connection: go to Network > Network Test and run a ping test to 8.8.8.8. If the ping fails, check the Ethernet cable between the NVR and your router.

Jadaol Cat 6 Ethernet Cable 25 ft, 10Gbps Support Cat8 Cat7 Network, Flat RJ45 LAN Patch Cable, High-Speed Wired Internet Cable for Router, Modem, Switch, Gaming Consoles, PC, Streaming Devices, Black

Needed for this step

Jadaol Cat 6 Ethernet Cable 25 ft, 10Gbps Suppo...

This helps complete the fix you are currently reading.

$9.99
View Needed Item
2

Enable P2P or cloud access on the NVR

Lorex NVRs use P2P (peer-to-peer) for remote access — no port forwarding required. On the NVR, go to Main Menu > Network > P2P (or Cloud). Make sure P2P is enabled and the status shows Online or Connected. If it shows Offline, the NVR cannot reach the Lorex cloud relay. Check your internet connection and make sure your router does not block outbound connections on the ports Lorex uses (typically HTTPS/443).

3

Set up the Lorex Home app for remote access

Open the Lorex Home app. Add the NVR by scanning the QR code on the NVR body (usually a sticker on the top or bottom). Or manually enter the Device ID shown on the NVR P2P settings page. Enter the NVR admin password. The app connects to the NVR through the Lorex cloud relay. You should see live feeds from all connected cameras. If the app connects but shows no video, the NVR may need a firmware update.

4

Fix slow or buffering remote video

Remote viewing quality depends on your home internet upload speed. At home, the NVR streams video to the cloud at your connection upload speed. Most ISPs provide much lower upload than download. For smooth remote viewing: check your upload speed (run a speed test at home — you need at least 5 Mbps upload for one 1080p stream, 10 Mbps for multiple). In the NVR, go to Camera > Encode > Sub Stream. Set the sub stream to 720p or D1 resolution — the app uses the sub stream for remote viewing. Lower sub-stream resolution requires less bandwidth.

5

Use port forwarding as an alternative to P2P

If P2P is unreliable, you can set up port forwarding on your router for direct NVR access. On the NVR, note the HTTP port (default 80 or 8080) and the client port (default 35000). In your router settings, forward these ports to the NVR internal IP address. Then in the Lorex app, add the NVR using IP Address mode and enter your public IP. Note: port forwarding exposes the NVR to the internet — change the default admin password to something strong and consider using a VPN instead for better security.

Quick Solutions

Confirm the NVR is connected to the internet (cable to the router)
Enable P2P/cloud in the NVR and add it by UID/QR in the app
Configure port forwarding and DDNS for manual setups
Check the router firewall; enable UPnP or open the needed ports
Verify adequate upload bandwidth at the NVR location
Re-enter the correct login credentials in the app
Resolve double NAT/CGNAT (bridge mode or ISP public IP)
Update the NVR firmware and the Lorex Home app

Still having issues? This is usually the deeper cause below.

If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.

Pro Tip

Set up activity zones to monitor only the areas that matter like your front porch and driveway and exclude the street. This dramatically reduces false alerts while ensuring you never miss an actual event at your property.

Real-World Insight

This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.

What Usually Goes Wrong
  • NVR/system has no internet connection
  • Router blocking the connection (firewall/UPnP off)
  • P2P/cloud connectivity not enabled or UID not added
  • Port forwarding/DDNS not configured (manual setups)
  • Low upload bandwidth at the NVR site

Official Manufacturer Manual

Lorex provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Lorex NVR/DVR.

View Lorex NVR/DVR Online Manual

Source: lorex.com

Need More Help? Lorex Support

Note: The contact information below connects you directly to Lorex's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.