---
title: "Troubleshooting"
slug: "kproxy-migration-troubleshooting"
description: "Troubleshoot common issues when migrating from Kentik kproxy to Universal Agent. Learn how to resolve Agent Status 'Down' (Exit 10), fix missing interface names, and verify SNMP polling or firewall connectivity."
updated: 2026-03-04T22:50:04Z
published: 2026-03-04T22:50:04Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.kentik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

While you [**migrate from kproxy to the Universal Agent**](/v1/docs/migrate-from-kproxy-to-universal-agent), if you encounter issues, consult the table below for common symptoms and their resolutions (see also: [**FAQ**](/v1/docs/kproxy-migration-faq)).

| Symptom | Technical Root Cause | Resolution |
| --- | --- | --- |
| **Agent Status "Down" (Exit 10)** | Configuration validation failure | Ensure Site and **My Network** fields are assigned in the portal under **Settings »** **Universal Agents**. |
| **Agent Status "Up" but No Data** | Local firewall or routing path blockage | - Check local host firewalls (e.g., `iptables`, `ufw`, or `firewalld`). - Verify that flow traffic is actually reaching the host by running `sudo tcpdump -i any port 9995`. |
| **Missing Interface Names (Showing Index IDs)** | SNMP connectivity or polling failure | - Verify the **SNMP/ST** capability is installed and showing an "Up" status. - Ensure the SNMP tab in Device Settings is set to **Agent-based SNMP for Flow Enrichment**. - Ensure community strings are correct. |
| **SNMP Polling Fails Post-Migration** | Credential mismatch | Verify that the SNMP v2c/v3 strings and passwords in **Organization Settings »** **Credentials Vault** exactly match the device configurations. |