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

# sk182028 - API commands fail with "Could not connect to API server" error

| Property | Value |
|----------|-------|
| Solution ID | sk182028 |
| Date Created | 2024-02-15 |
| Last Modified | 2025-11-19 |
| Technical Level | Advanced |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20 |

## Symptoms

- * An error occurs when running API commands, for example:  

  `
  # mgmt_cli -r true login`  
  `
  Error: Could not connect to API server, check 'api status' for more details.`

* The command: `# cat /web/conf/extra/httpd-ssl.conf | grep "Listen <YOUR-HTTPS-PORT>"` returns an empty output. (The HTTPS port number can be 443, 8443, or 9443.)

## Cause

Missing HTTPS port configuration line in the */web/conf/extra/httpd-ssl.conf* file.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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