---
title: "Troubleshooting"
slug: "troubleshooting"
updated: 2026-05-11T16:14:23Z
published: 2026-05-11T16:14:23Z
---

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

# Troubleshooting

| **PROBLEM** | **RESOLUTION** |
| --- | --- |
| Compute node does not show up in Fortanix Confidential Computing Manager (CCM). | We have an account quota that limits the total active compute nodes. Delist an existing node to add a new node. Run the following command to check the status of `em-agent` service on your system: ```bash sudo systemctl status em-agent ``` Where, `em-agent.service` is the Fortanix CCM Agent. In case of error, run the following command to check the detailed logs of `em-agent` service: ```bash journalctl -f -u em-agent.service ``` |
| Getting the error - 'Failed to connect to any resolved endpoint' with my application. | Check if the value of `NODE_AGENT` matches your compute node IP. `ifconfig -a` should show you all the IPs. Run the following command to check the status of the node agent service: ```bash sudo systemctl status em-agent ``` Where, `em-agent.service` is the Fortanix CCM Agent. |
| A converted app fails with error. | This error occurs when the `NODE_AGENT` environment variable is incorrectly passed. Use the IP for the node as shown in Fortanix CCM UI or in the `journalctl -u em-agent` log as `NODE_AGENT` environment variable. |

## Related

- [Fortanix CCM - Quickstart](/quickstart-guide.md)
- [PKCS#11 Library](/clients-pkcs11-library.md)
- [Logging](/users-guide-logging.md)
- [Fortanix DSM as a KMS to Secure VMware Virtual Environments](/using-fortanix-data-security-manager-as-a-kms-to-secure-vmware-virtual-environments.md)