Live view was working last week. Now the feed won’t load, the vehicle shows as offline, or the connection drops as soon as it establishes. The vehicle is out on the road, the driver says nothing is wrong with the camera, and you have no way of checking what’s happening.
Troubleshooting live view connection issues in fleet cameras is not the same as fixing a camera that has stopped recording. Recording can continue locally even when the remote connection is broken. The issue is almost always in the transmission path between the camera system and the platform — not in the camera itself.
This guide covers the most common causes, a structured diagnostic sequence, and the specific scenarios that trip up even experienced fleet managers who have had live view running without problems for months.
Before diagnosing what is broken, it helps to understand what a working live view connection actually requires. There are four dependencies, and all four need to be functioning simultaneously.
Most live view connection failures come down to one of these four. The diagnostic sequence below works through them in order of likelihood.
Open the platform and check the vehicle’s last known GPS location and the time of its last data transmission. If the vehicle is showing as offline or has not updated its position in more than a few minutes, the cellular connection has dropped.
This is the most common cause. Fleet cameras rely on the same cellular infrastructure as any other connected device, and signal quality varies by location, time of day, and network congestion. A vehicle that was in a good signal area yesterday may be in a weak-signal area today.
If signal is the issue: check whether the vehicle is in a known dead zone, wait for it to move to better coverage, or contact the driver to confirm the camera power indicator is on. There is nothing further to troubleshoot on your side until the vehicle has a working data connection.
Log into your fleet platform’s account or billing section and confirm that the live view feature is included in the current subscription. This is more common than it sounds. Subscriptions renew annually, payment details change, and feature tiers get restructured when suppliers update their pricing. It is entirely possible for live view to be removed from an account without anyone realising — until someone tries to use it and it no longer appears as an option.
If the live view option is missing from a vehicle’s menu entirely, start here rather than with technical diagnostics.
A version mismatch between the MDVR firmware and the fleet management platform is a consistently underdiagnosed cause of live view failures. Forum users troubleshooting connection issues repeatedly find that after an automatic platform update, live view stops working on vehicles that have not yet received the corresponding firmware update — or vice versa.
Check the firmware version currently running on the MDVR (usually visible in the device settings or via the platform’s device management screen) and compare it against the version the platform expects. If there is a discrepancy, a firmware update to the affected vehicles will typically resolve the connection.
This is the cause that surprises fleet managers most often, and it is worth checking on both the viewing device and the office network.
If VPN software is running on the device you are using to access the platform — even in the background — it may be redirecting traffic in a way that prevents the live stream from establishing. The most reliable test is to disable the VPN entirely and try the live view connection again. If it connects, the VPN configuration is the issue. Most corporate VPN software allows individual applications or destinations to be excluded (a “split tunnel” configuration); your IT team can add the fleet platform’s domain to that exclusion list.
Similarly, corporate firewalls sometimes block the specific ports or protocols that live view streaming uses. If live view works on a mobile data connection but not on the office WiFi, the office firewall is the most likely cause. Your IT team will need to whitelist the streaming endpoints used by your fleet platform — the supplier can provide the specific addresses and port requirements.
Before escalating to your supplier, test live view from a completely different device on a completely different network — ideally a mobile phone on 4G data rather than office WiFi. If live view works on the phone but not the desktop, the issue is local to your viewing environment (VPN, firewall, browser, or proxy settings). If it also fails on the phone, the issue is more likely at the vehicle or platform level.
Browser compatibility is also worth checking. Some fleet platforms require specific browser versions or have known issues with certain combinations of browser and operating system. Clearing the browser cache and trying a different browser takes two minutes and resolves a surprising number of unexplained failures.
If Steps 1–5 do not resolve the issue, the fault is likely in the vehicle — either the MDVR, the SIM card inside it, or the power supply to the system.
The SIM card inside the MDVR provides the cellular data connection. SIM cards can be deactivated by the network operator if data usage limits are hit, if the account associated with the SIM is in arrears, or if the card itself has failed. Your fleet platform supplier or telematics provider will be able to check the SIM status remotely and confirm whether data is active on that device.
Power supply issues are worth checking if the vehicle has recently had other electrical work done, if the camera indicator lights are behaving differently than normal, or if the MDVR appears to be in a restart cycle. A voltage drop — caused by a poor connection at the fuse, a failing vehicle battery, or a loose wiring joint — can cause the MDVR to reset repeatedly, which prevents any stable data connection from establishing.
Most live view connection problems are predictable and preventable. The patterns that appear repeatedly across fleet operators are:
Escalate when: you have completed the diagnostic sequence above and cannot identify the cause; the issue affects multiple vehicles simultaneously (which points to a platform-level problem rather than a vehicle problem); or live view was working on a vehicle and has stopped without any changes being made.
When you contact your supplier, give them the vehicle registration, the MDVR serial number, the time the issue was first noticed, the firmware version, and the result of the different-device test. This information allows the supplier to check the SIM status, platform logs, and device health remotely without a site visit, which typically cuts the resolution time from days to hours.
Why does live view connect on some vehicles but not others? If live view works on most of your fleet but fails consistently on specific vehicles, the issue is almost always vehicle-specific: SIM status, MDVR firmware version, or a power supply issue. Check the affected vehicles’ firmware versions against the rest of the fleet and confirm the SIM is active.
Live view worked yesterday — what changed? The most likely candidates are: a platform update that introduced a firmware compatibility requirement; a VPN or firewall rule change at the office; a SIM data allowance being hit; or the vehicle entering a poor signal area. Work through the diagnostic sequence in order — cellular signal first, then the viewing environment.
Why does live view work on my phone but not the office desktop? This confirms the issue is in the office viewing environment, not the vehicle or platform. Check whether VPN software is running on the desktop, whether the office firewall is blocking the streaming ports the platform uses, and whether the browser needs updating or its cache clearing.
How do I know if the MDVR SIM card has been deactivated? Contact your fleet platform supplier and give them the MDVR serial number. They can check the SIM status remotely. Signs that the SIM may be inactive include the vehicle showing as permanently offline despite the camera being powered on and the indicator lights appearing normal.
Can a firmware update break live view? Yes. If the platform updates and the MDVR firmware has not been updated to match, compatibility issues can break the live view connection even though recording continues normally. Always ask your supplier whether a platform update requires a corresponding firmware update on MDVRs.
What ports does live view use, and do I need to tell IT? Live view streaming typically uses RTSP (port 554) or RTMP (port 1935) alongside HTTPS (port 443). Your supplier can provide the exact ports and streaming endpoint addresses for whitelisting. If your office runs a corporate firewall or uses a web content filter, IT will need to whitelist these to allow live view to function.
Why does live view drop after a few seconds? A connection that establishes then drops immediately suggests a borderline signal level — strong enough to initiate the connection but not to sustain the stream. Check the vehicle’s location and signal strength in the platform. It may also indicate a power supply issue causing the MDVR to reset under load.
Do I need to be in the office to access live view, or can I use it remotely? Most fleet platforms allow live view access from any device with an internet connection and the right credentials. However, if your organisation uses a VPN that routes all traffic through the office network, remote access may be subject to the same firewall rules as office access. Confirm your VPN configuration allows direct access to the fleet platform’s streaming endpoints.
A step-by-step checklist to diagnose live view connection failures — covering cellular signal, subscriptions, firmware, VPN interference, and vehicle-side faults.
Related guides: How Live View Integrates With MDVR Systems · Live View Monitoring Checklist for Fleet Managers
4 August 2026
Monday to Friday:
8.30am-5.30pm
