This article outlines the required settings that your Verkada Access Controllers need to communicate with Verkada Command and to operate properly.
Requirement: Verkada devices are incompatible with LANs that require the use of proxy servers or that require Secure Socket Layer (SSL)/Transport Layer Security (TLS) inspection. If either are in use, a bypass for all Verkada devices must be implemented for Verkada devices to communicate with Command.
Status LED
At the top left of the physical access controller, you see a flashing blue status LED. This LED indicates that the access controller is not communicating with Command.
If you see this behavior:
Check that the network is set up correctly for the access controller.
See Verkada Access Offline Operation to understand what the access system does when it cannot communicate with Command.
If the problem persists, contact Verkada Support.
Power
See the Access Control (datasheet) for your access controller’s power requirements.
IP address
Access controllers need an IPv4 address to communicate on the local area network (LAN) and to Command through the internet. Access controllers use Dynamic Host Configuration Protocol (DHCP), UDP ports 67 and 68, to obtain their IP addresses and network configurations.
If you want to have a specific IP address on your access controller, set a DHCP reservation using the access controller’s Media Access Control (MAC) address (found on the device's label).
Domain Name System
Access controllers use the DNS server to resolve Verkada’s fully qualified domain names (FQDN) to IP addresses to communicate with them. Your DHCP server tells the access controller where the DNS server is on the network and the device using UDP port 53.
Note: DNS over HTTPS (DoH) is currently not supported.
Firewall settings
Verkada devices require access to many endpoints to have the full-featured experience. Many customers may want to restrict devices to only communicate with the specific required endpoints.
These are the general domains to allow, applicable for all organization-regions:
*.verkada.com - UDP/123 + TCP+UDP/443
34.216.15.26 - UDP/123
35.166.49.153 - UDP/123 + TCP+UDP/443
If your firewall does not allow wildcard masking, or you prefer to have the entire FQDN of the endpoint in your firewall rules, these are the domains to allowlist, by region:
Region: United States
Note: Your region is selected when you create an organization in Command.
35.166.49.153 - UDP/123 + TCP+UDP/443
vcerberus.command.verkada.com - TCP+UDP/443
access.control.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
api.control.verkada.com - TCP+UDP/443
relay.control.verkada.com - TCP+UDP/443
index.control.verkada.com - TCP+UDP/443
firmware.control.verkada.com - TCP+UDP/443
update.control.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
user.pyramid.verkada.com - TCP+UDP/443
device.pyramid.verkada.com - TCP+UDP/443
nlb.verkada.com - TCP+UDP/443
device-nlb.verkada.com - TCP+UDP/443
34.216.15.26 - UDP/123
Region: Europe
Note: Your region is selected when you create an organization in Command.
35.166.49.153 - UDP/123 + TCP+UDP/443
vcerberus.command.verkada.com - TCP+UDP/443
relay.prod2.control.verkada.com - TCP+UDP/443
api.prod2.control.verkada.com - TCP+UDP/443
access.prod2.command.verkada.com - TCP+UDP/443
api.global-prod.control.verkada.com - TCP+UDP/443
relay.global-prod.control.verkada.com - TCP+UDP/443
vconductor.global-prod.command.verkada.com - TCP+UDP/443
index.prod2.control.verkada.com - TCP+UDP/443
update.control.verkada.com - TCP+UDP/443
vconductor.prod2.command.verkada.com - TCP+UDP/443
time.control.verkada.com - UDP/123
Related resources
Video Security Network Settings (Cameras)
Workplace Network Settings (Guest, Mailroom)
Visit the Verkada Training Center for bite-sized video tutorials on how to accomplish role-based tasks in Command.
Need more help? Contact Verkada Support