Why remote monitoring stops working
If you can no longer access cameras remotely (only locally on the recorder), there are several possible causes:
1. Internet connection
Verify that the recorder is connected to the internet — open settings on the recorder, look at network status. If there is no IP address or the gateway is missing, the network connection is broken. Check the cable, switch, router.
2. Public IP / port forwarding
If you used a public IP and port forwarding, your ISP may have changed:
- Public → private IP (CGNAT) — you can no longer be reached from outside.
- Dynamic IP — the IP changed and old DDNS/host names point to the wrong address.
- Blocked ports — the ISP blocked common ports (e.g. 80, 8000).
Solution: switch to P2P (no public IP needed) or contact the ISP to restore a public IP.
3. P2P cloud server
Sometimes the manufacturer's P2P cloud servers experience load or maintenance. Try logging in after a few minutes. Check status pages.
4. Outdated firmware
Old firmware may not be compatible with the new P2P protocol. Update firmware via the web interface or USB.
5. Account problems in the BitVision app
- Try logging out and back in.
- Reinstall the app (saves device list to cloud).
- Try a different account or remove and re-add the device.
6. Router / NAT settings
The router was rebooted or its settings changed. Verify port-forwarding rules in the router settings (typically Advanced → Virtual server / Port forwarding).
Diagnostic checklist
- Does the recorder show internet status OK in network settings?
- Does the device's cloud ID respond in the app?
- From outside (mobile data, not home WiFi), can you reach the public IP?
- Are the ports forwarded in the router (try a port-checker tool)?
- Is the firmware up to date?
For technical questions contact support@patronum.eu.