Ubios-udapi-server | Confirmed 2025 |

# On the UniFi OS device
podman logs unifi-core --tail 100
ubios-udapi-server is a core background service (daemon) running on Ubiquiti’s UniFi Dream Machine (UDM), UniFi Dream Machine Pro (UDM-Pro), and UniFi Dream Router (UDR) product lines. It serves as the local API gateway and interaction layer between the UniFi OS (the operating system managing the device) and the UniFi Network Application (the controller software).
In the transition from the older, cloud-key based architecture (where the controller was software separate from the gateway) to the "all-in-one" Dream Machine architecture, Ubiquiti needed a way for the controller software to communicate with the underlying system services (firewall, DHCP, DNS, etc.). ubios-udapi-server fulfills this role.
Schedule a cron job on your automation server to hit:
GET /proxy/network/api/s/default/stat/report/daily and pipe the JSON into a CSV for your accounting department.
ubios-udapi-server is the unsung workhorse of UniFi OS local management. Understanding it unlocks powerful automation, faster troubleshooting, and deeper integration with your UniFi network – all while keeping control local. If you’re writing scripts or building tools for UniFi, learning its endpoints is time well spent.
ubios-udapi-server is a critical system service in Ubiquiti UniFi OS, primarily found on hardware like the UniFi Dream Machine (UDM) . It serves as the primary configuration management engine
, bridging the gap between the UniFi Controller's high-level settings and the low-level Linux networking tools that execute them. Core Functions and Architecture UDAPI Framework
: The service utilizes the Universal Dependencies API (UDAPI) framework to aggregate network configurations provided by the controller into a unified JSON format. State Management
: It maintains the operational state of the device, often stored in files like /data/udapi-config/udapi-net-cfg.json /config/ubios-udapi-server/ubios-udapi-server.state Process Orchestration
: The server is responsible for launching sub-processes and passing runtime arguments to various network components based on the consolidated JSON configuration. Component Initialization
: It handles the setup of critical networking features, such as: DHCP Services : Manages DHCP resiliency and client compliance. Firewall & Routing : Coordinates firewall rules and port/address groups. Security Services : Orchestrates security tools like Suricata for IPS/IDS
: Manages RADIUS server certificates for network authentication. Common Issues and Monitoring ubios-udapi-server
While vital, users often encounter specific technical hurdles with this process:
The ubios-udapi-server is a core background process (daemon) within Ubiquiti's UniFi OS, specifically acting as the primary configuration engine and API interface for Dream Machines (UDM, UDM-Pro) and newer Cloud Gateways. It serves as the "brain" that translates your high-level GUI clicks into actual low-level system configurations. 🧠 The "Brain" of the Gateway
While the UniFi Network Application provides the visual interface, ubios-udapi-server handles the heavy lifting underneath. It is responsible for:
Provisioning: Applying settings like firewall rules, VLANs, and VPN configurations to the hardware.
Service Management: Orchestrating background services like DHCP, DNS (via dnsmasq), and routing tables.
Deep Packet Inspection (DPI): Managing the flow of traffic data to provide the statistics seen in the UniFi dashboard.
Real-time Monitoring: Running health checks and WAN failover logic to ensure the internet connection is active. 🛠️ Performance & "Behind the Scenes"
Because it is so central to the device's operation, it is often a focal point when performance issues arise:
Resource Intensity: Users have reported that high DPI traffic or large database operations (like MongoDB mass deletes) can sometimes block the process, leading to temporary packet loss or a sluggish UI.
Memory Footprint: In some firmware versions, memory leaks associated with this process have caused gateways to reboot after extended uptime as usage climbs toward 100%. # On the UniFi OS device podman logs
Stability Fixes: Ubiquiti frequently includes "Application Stability" improvements in release notes which often target the efficiency of this specific server to prevent these crashes. 🔍 Troubleshooting Insights
If you are digging into system logs via SSH, here is what ubios-udapi-server entries usually mean:
"DPI stats update already in progress": Often a harmless warning, but if repeated frequently, it may indicate the system is struggling to keep up with high traffic volumes.
Port Conflicts: If the server fails to start, it is usually due to another manual process (like a custom Docker container) grabbing a port it needs for its internal API.
WAN SLA Probes: It periodically pings ping.ui.com and checks DNS against Cloudflare (1.1.1.1) and Google (8.8.8.8) to determine if your internet is "up".
💡 Key Takeaway: If your UniFi dashboard is slow or "Gateway Configuration Failed" messages appear, the ubios-udapi-server is likely the process experiencing a bottleneck.
Are you looking to troubleshoot a specific error message, or are you interested in how to optimize its performance on a specific device like a UDM-Pro or UCG-Fiber?
ubios-udapi-server is a central service running on Ubiquiti’s UniFi OS devices, such as the UniFi Dream Machine (UDM) and UXG series. It acts as a configuration and management bridge between the UniFi Network application and the underlying Linux operating system. Executive Summary ubios-udapi-server
is responsible for translating high-level network configurations (VLANs, firewall rules, routing) into low-level system commands. It manages essential features like Deep Packet Inspection (DPI)
and Intrusion Detection Systems (IDS/IPS) by coordinating with engines like Suricata. Core Responsibilities Configuration Migration All without constantly opening SSH sessions
: It handles the transition of settings during firmware updates, ensuring that parameters like .versionDetail remain valid to prevent boot loops. Security Integration
: The server manages the configuration for Suricata, located at /usr/share/ubios-udapi-server/ips/ , enabling threat detection and blocking capabilities. State Management
: It maintains a real-time state of the device’s networking stack (Firewall, NAT, etc.) in a JSON-formatted file usually found at /run/ubios-udapi-server/ubios-udapi-server.state Common Use Cases & Troubleshooting IDS/IPS Tuning
: Advanced users often inspect the server's logs or state files via SSH to troubleshoot why specific security rules are or aren't being triggered. Network Provisioning Issues : If a configuration change (like a WAN IP update ) fails to apply, the ubios-udapi-server
state can reveal if the command was rejected or if the underlying configuration is inconsistent. Memory & Performance
: As a critical service, its resource consumption is often monitored. Sudden spikes in RAM usage can indicate firmware-specific bugs affecting system stability. Service Interaction Table Interaction with ubios-udapi-server Firewall/NAT Translates UniFi UI rules into Configures and launches Suricata in PCAP or NFQUEUE mode. Manages tunnel state and remote access credentials. Network Migration Validates schema versions during UniFi OS upgrades. of its API endpoints or specific logs to look for during a crash?

Ubiquiti Networks utilizes a proprietary architecture known as UniFi OS to power its Dream Machine (UDM, UDM-Pro, UDR), UniFi Cloud Key Gen2, and high-end Enterprise hardware. Unlike traditional standalone devices, UniFi OS runs a containerized operating system where the control plane (the Network Application) is decoupled from the data plane (the hardware switching/routing logic).
The ubios-udapi-server acts as the glue in this architecture. Before the introduction of UDAPI, interaction with devices often relied on low-level system calls or custom scripts. UDAPI standardizes this into a uniform API, allowing the UniFi Network Application to manage devices regardless of the specific chipset or firmware version, provided they support the UniFi OS architecture.
Out of the box, the ubios-udapi-server is dormant. You must enable it. Here is the step-by-step process.
Historically, UniFi controllers communicated with devices directly via SSH + JSON. That worked, but had scaling and security limitations. With newer UniFi OS releases (especially on consoles), Ubiquiti moved toward a more structured, socket-based, and secure internal API.
ubios-udapi-server handles:

All without constantly opening SSH sessions.