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

# sk181928 - Security Gateway does not apply NAT to HTTPS connections sent from external clients to Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk181928 |
| Date Created | 2024-01-28 |
| Last Modified | 2025-01-16 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- The Inbound HTTPS Inspection policy does not inspect HTTPS connections that external clients send to the Security Gateway.

This applies specifically to connections on which the Security Gateway must perform NAT and forward to an internal server.

## Cause

By default, the Security Gateway does not apply NAT to HTTPS connections when the destination IP address belongs to the Security Gateway.

It assumes that traffic destined to the Security Gateway does not require inspection.

Therefore, the HTTPS Inspection bypasses these connections.

## 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