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

# sk182684 - "Error: Update of the Network Feed 'OBJECT NAME' failed because the Security Gateway could not reach the destination" log from a Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk182684 |
| Date Created | 2024-10-09 |
| Last Modified | 2025-04-24 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20 |
| OS | Gaia |

## Symptoms

- * "`Error: Update of the Network Feed 'OBJECT NAME' failed because the Security Gateway could not reach the destination`" log from a Security Gateway.

  Example:

  ![](https://sc1.checkpoint.com/sc/SolutionsStatics/NEW_SK_NOID1726297718546/efo_update_failed202409141540341.jpg)
* In SmartConsole, in the Network Feed object, the "**Test Feed**" action ends with the same error.

* Connection from the Security Gateway to the feed file is successful (with the "`curl_cli -k <Full URL>`" command).

* The `$FWDIR/log/efo_error.elg` file on the Security Gateway contains this error:

  `[<DATE TIME>][<NAME of FEED OBJECT>]: EFO_FEED> get_domain_from_url: called with URL <URL OF FEED>/<NAME OF FEED FILE>`  
  `
  [<DATE TIME>][<NAME of FEED OBJECT>]: EFO_FEED> get_domain_ips: called with name <URL OF FEED>`  
  `
  [<DATE TIME>][<NAME of FEED OBJECT>]: EFO_FEED> get_domain_ips: failed to resolve the domain name, res=-1`  
  `
  [<DATE TIME>][<NAME of FEED OBJECT>]: EFO_FEED> validate_feed_url: error: could not resolve the domain`

## Cause

The Network Feed object update fails because its URL contains a port number.

By default, a port number is not supported in the Network Feed URL.

Example:

`https://myserver.example.com`:8080`/my_feed_file.csv`

## Solution

This problem was fixed. The fix is included starting from:

* [Check Point Quantum R82](https://support.checkpoint.com/results/sk/sk181127)
* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 89

If you choose not to upgrade, [contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for your version.

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).

<br />

The immediate **workaround** is:

1. Change the configuration on the feed server to serve the feed file over these TCP ports:
   1. For HTTP - over the TCP port 80
   2. For HTTPS - over the TCP port 443
2. In SmartConsole, in the Network Feed object:
   1. In the **Feed URL** field, remove the port number.
   2. Click the "**Test Feed**" button and make sure the test is successful.
3. Install the Access Control policy.

---

# 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