Resolving Verkada Wi-Fi Connectivity Issues
Ensuring your Verkada cameras, access control, and sensors have a stable Wi-Fi connection is fundamental to the security of your organisation. When a device fails to connect or frequently drops offline, it creates a critical visibility gap. This guide is designed for IT professionals and network administrators to systematically troubleshoot and resolve Wi-Fi connectivity problems with Verkada hardware.
### Core Requirements for Verkada Device Connectivity
Unlike consumer-grade devices, Verkada's enterprise solution has specific network requirements for security and reliability. A failure to meet these is the most common source of issues.
- Firewall Configuration: Devices must be able to communicate with the Verkada Command cloud. This requires outbound access on TCP port 443.
- Time Synchronisation: Network Time Protocol (NTP) is used to keep device time accurate. UDP port 123 must be open for outbound traffic.
- Sufficient Signal Strength: A weak or fluctuating Wi-Fi signal will lead to packet loss, video degradation, and disconnections.
- Correct Wi-Fi Band: Ensure the device is connecting to a supported band (2.4GHz or 5GHz) as specified in its datasheet.
A Systematic Troubleshooting Workflow
Follow these steps to diagnose and resolve connectivity problems with any Wi-Fi-enabled Verkada device.
### 1. Verify Firewall and Port Access
This should always be your first check.
- Confirm with your network security team that outbound traffic is allowed to
*.verkada.comon TCP port 443. - Verify that outbound UDP traffic on port 123 is also permitted for NTP.
- Check for any web content filters or proxy servers that might be inspecting or blocking the SSL traffic from the Verkada device to the cloud. If necessary, create a bypass rule for the camera's IP address.
### 2. Assess Wi-Fi Signal Strength and Quality
A poor wireless environment is a frequent culprit.
- Measure Signal Strength: Use a Wi-Fi analytics tool (such as a mobile app or professional surveyor) at the device's physical location. The Received Signal Strength Indicator (RSSI) should ideally be -65 dBm or stronger (e.g., -60, -55 dBm). An RSSI of -70 dBm or weaker is likely to cause problems.
- Check for Interference: Use the analyser to identify channel congestion. If multiple access points are competing on the same channel, it can degrade performance. Manually set your access point to a less crowded channel.
- Ensure Proper AP Placement: If the signal is weak, the wireless access point may be too far away, or there may be dense physical obstructions (concrete walls, metal shelving) in the way. Consider repositioning the AP or installing a new one closer to the device.
### 3. Check Network Access and Authentication
- MAC Address Filtering: If your network uses MAC address whitelisting, ensure the Verkada device's MAC address (found on the device's label) has been added to the 'allow' list on your wireless controller or RADIUS server.
- Confirm Wi-Fi Credentials: Double-check that the SSID and password configured for the device are 100% correct.
- Captive Portals: Verkada devices cannot navigate captive portals (the login pages often found on guest networks). They must be connected to a network that provides direct internet access after authentication, such as one using WPA2-Personal or WPA2-Enterprise.
### 4. Power Cycle and Check Device Status
- Reboot the Device: Perform a hard reboot by disconnecting the device from its power source (PoE or power adapter) for 30 seconds.
- Observe the Status LED: The LED light on the device provides valuable diagnostic information. For example, a solid orange light typically means it's on but cannot reach the Verkada servers, while a flashing blue light indicates a connectivity attempt is in progress. Refer to the specific device's documentation for a full list of LED status codes.
By methodically validating these four key areas—firewall rules, Wi-Fi environment, network authentication, and device status—you can efficiently resolve the vast majority of Verkada connectivity issues.