First establish local live view and recent playback, then configure the approved remote-access method for the exact recorder and app. Local recording and remote viewing are separate paths: an app connection error does not by itself mean that recording stopped.
Choose and document the access method
| Path | Setup check |
|---|---|
| Supported app / P2P | Use the app and account process for the exact device; check its network and remote-service status. |
| Managed VPN | Confirm the authorized VPN reaches the site, then test the recorder address and user permissions. |
| Supported browser access | Confirm browser support and the administrator-approved network path. Local browser access alone does not prove remote access. |
Record the device/app versions, address assignment, gateway, DNS and responsible administrator. DDNS provides a hostname; it does not create a secure access path. Keep account permissions and update procedures in the remote-access security plan.
If local viewing works but remote access fails
- Test the same authorized account and device on site, then using cellular data or another trusted network. Save the exact error and time.
- Compare a second authorized phone or computer. One failing device points toward its app, account or network permissions. Every remote device failing points toward the shared connection or service.
- If supported, compare the normal viewing stream with a lower-bandwidth stream. If only the latter works, check available bandwidth and decoding before changing recording quality.
Check the recorder, router and service path
For app/P2P access, check the recorder's network and supported remote-service status. Use the device that manages the camera channels: a camera on the recorder's PoE network can have a different path from a standalone camera.
If another authorized device on the site network has internet while the recorder is offline, compare the recorder's network status, gateway and DNS with the approved site configuration. A working phone or computer does not prove that the recorder has the same access.
After a router replacement, compare the original configuration with address assignment, gateway, DNS and approved access method on the new network. Ask the administrator to review the relevant rules; broad firewall changes are not an initial diagnostic step.
For VPN, confirm the connection reaches the site before testing the recorder. App/P2P, VPN and browser access have different requirements; success with one does not prove the others work.
Verify access from outside the site
Check live view and a recent recording from outside the site network. Reconnect the app and recheck local recording. Record the change that restored access and keep the original configuration. If access still fails, send recorder/app versions, errors and local-versus-remote results through private support; do not post account credentials.
Technical references and related checks
Reolink remote camera checks and NVR remote checks support device/network comparisons. Their UID and app controls apply to Reolink equipment.
For missing local video or recordings, follow the CCTV troubleshooting paths. For events/audio in a mixed system, use the ONVIF compatibility checks.