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

# sk181159 - IPS Update for a specific Security Gateway fails with "Update failed. Could not reach "dl3.checkpoint.com". Check proxy configuration on the gateway."

| Property | Value |
|----------|-------|
| Solution ID | sk181159 |
| Date Created | 2023-06-29 |
| Last Modified | 2023-07-02 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * SmartConsole shows that IPS Update failed with one of these errors for a specific Security Gateway:

  * *Update failed. Could not reach "dl3.checkpoint.com". Check proxy configuration on the gateway.*

  * *Update failed. Gateway can not access internet ('http://dl3.checkpoint.com/\<PATH\>/sd_updates.upf?HashKey=\<VALUE\>'). Check connectivity and proxy settings.*

  This error appears in SmartConsole in these places:
  * From the left navigation panel, click the "Gateways \& Servers" view \> select the Security Gateway object \> in the bottom pane, click the "Summary" tab \> click the "Device \& License Information" link \> in the left pane, click the "Device Status" page \> expand the "IPS" section
  * From the left navigation panel, click the "Security Policies" view \> in the top middle panel, click the "Threat Prevention" section \> in the bottom middle panel "Custom Policy Tools", click the "Updates" page \> in the error, click "More Details"
* Changing the "IPS Update Policy" option in the Security Gateway object \> on the "IPS" page does not resolve the issue - neither "*The gateway automatically updates the IPS protections* ", nor "*Use IPS management updates*".

* The *$FWDIR/ips/update/ips_status.C* file on the Security Gateway contains the same error that appears in SmartConsole.

* The "`curl`" / "`curl_cli`" tests from [sk83520](https://support.checkpoint.com/results/sk/sk83520) show that the connection between Security Gateway and Check Point servers is working.

## Cause

Debug of the FWD process on the Security Gateway during an IPS update shows (in the *$FWDIR/log/fwd.elg* file) that at some point, a peer resets and closes the connection from the Security Gateway.

Example:

`[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [INFO] WriteMemoryCallback: 1076 chars 1076 were written to file.`  
`
[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [INFO] WriteMemoryCallback: 2896 chars 3972 were written to file.`  
`
......`  
`
[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [INFO] WriteMemoryCallback: 1448 chars 7545156 were written to file.`  
`
[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [INFO] WriteMemoryCallback: 2896 chars 7548052 were written to file.`  
`
[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [INFO] WriteMemoryCallback: 1448 chars 7549500 were written to file.`  
`
Recv failure: Connection reset by peer`  
`
Closing connection 0`  
`
[FWD 8142 3478125376]@Gateway[9 Jun 16:06:35] [ERROR] http_client_handle_finished_download: Operation failed. curl returned: Errorcode=56. Error String:Failure when receiving data from the peer`

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