Support

Why P2P Remote Viewing Stops Working

When P2P remote viewing stops working, the fault is usually not random. It is usually a router change, a cloud-status problem, a DNS or gateway issue, a double-NAT path, or the wrong app account.

Technical Support Guide

Summary

Use this guide when remote viewing worked before and then stopped, or when the cloud path never came online properly after setup.

Applies to

  • Hikvision, HiLook, Dahua, Uniview and similar cloud-app CCTV paths
  • NVRs and cameras using P2P or cloud relay
  • Sites affected by router, ISP or account changes

Difficulty and time

Difficulty: Moderate

Estimated time: 15 to 40 minutes

What you will need

  • Model details
  • Access to the recorder or camera locally
  • Router details if available
  • Phone for mobile-data testing
  • Screenshots or photos of network and cloud status

What this guide covers

  • Confirm the local device path
  • Check cloud or P2P status
  • Review router, DNS and gateway changes
  • Check account ownership and mobile-data behaviour

This guide is written for customers, installers and site managers who need a practical path when a cloud-based CCTV app suddenly stops working.

The quickest way to waste time here is to remove the device from the app before proving whether the recorder is still online. This page keeps the checks in the order that usually saves the most time.

Before you start

Write down the current behaviour before making changes. A clean baseline makes support much easier.

  • Note the exact model involved and which app is in use.
  • Take one screenshot or photo of the current offline or error status if possible.
  • Ask whether the modem, router, ISP or Wi-Fi gear changed recently.
  • Test one known scenario at a time.
Important

Do not guess your way through support changes

Change one thing at a time and test it properly before moving on.

Collect the model details and a clear symptom description if support needs to step in.

What usually causes this

  • The router or modem changed and the recorder still points at the old gateway or DNS path.
  • The cloud or P2P status on the recorder is offline even though the cameras still record locally.
  • The user is logged into the wrong owner or shared account.
  • A second router, mesh system or 4G backup created double NAT or a changed LAN path.
  • The site only tested on local Wi-Fi and never confirmed true remote access on mobile data.

Step 1: Confirm the local recorder or camera path first

Before changing settings, prove the recorder or camera is still healthy on site.

  • Confirm which recorder, camera or user is affected.
  • Confirm whether the issue is constant or intermittent.
  • Check whether recording and local live view still work.
  • Use one known test case rather than a broad assumption.

Step 2: Check the cloud or P2P status on the device itself

Most support jobs become easier once the recorder tells you whether it is actually online to the cloud service.

  • Open the P2P, Platform Access, or equivalent cloud-status page.
  • Check whether the device shows Online before touching the app.
  • Take a photo of the status screen.
  • Avoid assuming the app view tells the full story.

Step 3: Review gateway, DNS, router changes and double NAT

Once the local layer is proven, move to the network settings that usually break after site changes.

  • Check the current gateway and DNS entries on the recorder.
  • Ask whether the modem or ISP changed recently.
  • Look for a second router, mesh system, or backup internet device in the path.
  • Change one setting at a time and record what changed.

Step 4: Check account ownership and test on mobile data

Once the device is online locally and the cloud path looks healthy, confirm the app and user path.

  • Confirm the app is logged into the correct owner or shared account.
  • Turn Wi-Fi off and test on mobile data.
  • Repeat the exact test after any change.
  • If it still fails, collect model details and screenshots for support.
Worked example

Remote viewing died after a modem replacement

Situation: A small warehouse replaced its NBN modem and the cameras still recorded locally, but remote viewing stopped the next day.

Solution used: The recorder was still using the old gateway and blank DNS values. Once those were corrected and the cloud status returned to online, the app started working again without rebinding the recorder.

Why this was chosen: The fault was the network path, not the app account.

Installation notes: A mobile-data test confirmed the fix before the handover was closed.

Common mistakes

  • Deleting the device from the app before checking if the cloud service is actually online at recorder level.
  • Ignoring modem, router or ISP changes.
  • Skipping the mobile-data test and assuming local Wi-Fi proves remote access.
  • Changing several settings at once and losing track of the real fault.

Troubleshooting table

Symptom What to check What to do next
Recorder works locally but app is offline Cloud or P2P status, gateway, DNS, app account Open the device cloud-status page and confirm it is online before removing anything from the app.
Works on local Wi-Fi but not off site True remote cloud path, mobile-data test, router behaviour Test on mobile data and review the gateway, DNS, and double-NAT path.
Cloud page says offline Gateway, DNS, router changes, internet path Fix the recorder's route to the internet first.
Unsure whether support is needed Not enough evidence collected yet Take screenshots, model details and one clear symptom description before escalating.

When to contact support

Contact SecurityWholesalers support when you have the model details, one clear symptom description, and the basic local and settings checks have already been completed without solving the issue.

Related support guides

Related buying guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

  • What should I check first when P2P remote viewing stops working?

    Start at the recorder or camera, not the app. Confirm the device is still online locally and then check the cloud or P2P status before changing account settings.

  • What usually breaks P2P remote viewing?

    The most common causes are modem replacement, DNS or gateway changes, the device showing offline under its cloud service, double NAT, app account confusion, or a recorder that never came properly back online after a network change.

  • When should I contact support?

    After you have confirmed the model, the symptom and the basic local checks and still cannot resolve the issue.

  • Should I test locally before changing more settings?

    Yes. A local test usually tells you more than an app symptom alone.

  • What should I send support if I am still stuck?

    The order number if available, the product model, screenshots or photos of the current status, and a short note describing what you already tested.

Further Reading
Overview Overview Guide Page CCTV Networking Support Guide Page Hikvision Support Guides Guide Page HiLook Support Guides

Wrap up EOFY with extra bonus savings :) Use Coupon code: EOFY26 on orders over 800.
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Send Cart Email
Your cart email sent successfully :)