> Source: [sk182328](https://support.checkpoint.com/results/sk/sk182328)

# sk182328 - Proxy Gaia API request fails after enabling Identity Awareness API

| Property | Value |
|----------|-------|
| Solution ID | sk182328 |
| Date Created | 2024-05-23 |
| Last Modified | 2024-05-27 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |

## Symptoms

- * After enabling Identity Awareness API on the target Security Gateway, Gaia API requests made through the Management Server proxy fail with the error:

  `
  {
  `  
  `
  "code": "err_gaia_api_send_command_failed",
  `  
  `
  "message": "Cannot send the command to the gateway: X.X.X.X"
  `  
  `
  }`

* The error does not happen with API requests made directly to the Security Gateway.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content