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

# sk182482 - The on-premises Security Management Server fails to connect to Infinity Portal when this Server has a proxy configured

| Property | Value |
|----------|-------|
| Solution ID | sk182482 |
| Date Created | 2024-07-09 |
| Last Modified | 2024-07-09 |
| Technical Level | General |
| Products | Security Management Server, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS) |

## Symptoms

- * From the Infinity portal under Smart-1 cloud in the Management that connected from the on-prem machine we can see error in status of no connectivity   
* The management Server able to reach: curl_cli -k https://portal.checkpoint.com/  
  curl_cli -k https://datatube-prod-westeurope.azurewebsites.net/datatube
* The issue occur after an upgrade to the Management Server  
* \[Expert@cp-smart1:0\]# mgmt_cli -r true show-cloud-services --port 4434 code: "err_infinity_network"  
  message: "Failed to check the connection status due to a connectivity issue -  
  cloudinfra-gw.portal.checkpoint.com: cloudinfra-gw.portal.checkpoint.com: Temporary failure in name resolution If required, configure a proxy server in the Global Properties in SmartConsole, or Gaia Portal.   
  For more details, see sk179105."  
* \[Expert@cp-smart1:0\]# curl_cli --proxy http://XXXXXXXXX --verbose-extended -v https://cloudinfra-gw.portal.checkpoint.com:443  
  \* Rebuilt URL to: https://cloudinfra-gw.portal.checkpoint.com:443/  
  \* Trying XXXXXXXXx...  
  \* TCP_NODELAY set  
  \* Connected to XXXXXXXx port 9090 (#0)  
  \* allocate connect buffer!  
  \* Establish HTTP proxy tunnel to cloudinfra-gw.portal.checkpoint.com:443  
  \> CONNECT cloudinfra-gw.portal.checkpoint.com:443 HTTP/1.1  
  \> Host: cloudinfra-gw.portal.checkpoint.com:443  
  \> User-Agent: curl/7.61.1-DEV  
  \> Proxy-Connection: Keep-Alive  
  \> \< HTTP/1.0 200 Connection Established  
  \< \* Proxy replied 200 to CONNECT request  
  \* CONNECT phase completed!  
  \* ALPN, offering http/1.1  
  \* \*\*\* Current date is: Fri Jun 7 12:42:03 2024  
  \* TLSv1.3 (OUT), TLS handshake, Client hello (1):  
  \* err is -1, detail is 2  
  \* CONNECT phase completed!  
  \* CONNECT phase completed!  
  \* \*\*\* Current date is: Fri Jun 7 12:42:03 2024  
  \* TLSv1.3 (IN), TLS handshake, Server hello (2):  
  \* err is -1, detail is 2  
  \* \*\*\* Current date is: Fri Jun 7 12:42:03 2024  
  \* TLSv1.2 (IN), TLS handshake, Certificate (11):  
  \* TLSv1.2 (OUT), TLS alert, unknown CA (560):  
  \* err is -1, detail is 1  
  \* errdetail=0x1416f086  
  ERR_lib_error_string: SSL routines  
  ERR_func_error_string: tls_process_server_certificate  
  ERR_reason_error_string: certificate verify failed  
  ERR_error_string: error:1416F086:SSL   
  routines:tls_process_server_certificate:certificate verify failed  
  \* SSL certificate problem: unable to get local issuer certificate  
  \* Closing connection 0 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: https://curl.haxx.se/docs/sslcerts.html  

  curl failed to verify the legitimacy of the server and therefore could not establish a secure connection t
* "Failed to communicate with Infinity Portal. Check the connection between your Quantum Management environment and Infinity Portal. Also, make sure your Quantum Management environment is connected to your Infinity account in Smart-1 Cloud."
* The Security Management Server is using proxy.

## Cause

The issue occur after installing R81.20 Take 53

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 70
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 152

If you choose not to upgrade, Check Point can supply a **Hotfix** . [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 the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

<br />

---

# 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