Solved

Getting Error while adding GCP Cloud Library

  • 1 August 2022
  • 5 replies
  • 660 views

Badge +2

Hi Team,

We are getting below error while configuring GCP Cloud library , below is the error. Can anyone suggest what could be the reason 


Cloud Activity Logs:
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: Connected to www.googleapis.com (142.250.76.202) port 443 (#0)
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: ALPN, offering http/1.1
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: successfully set certificate verify locations:
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info:   CAfile: none
  CApath: /etc/ssl/certs/
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: TLSv1.2 (OUT), TLS header, Certificate Status (22):
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: Unknown SSL protocol error in connection to www.googleapis.com:443
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] == cURL Info: Closing connection 0
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] CURL error, CURLcode= 35, SSL connect error
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] Curl Error: 35, POST https://www.googleapis.com/oauth2/v3/token
1914 77a 08/01 18:28:18 ### [CloudTestTool.e] retryable error [44038], retry = 9, sleep for 9 second(s)
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info:   Trying 172.217.27.202...
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: TCP_NODELAY set
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: Connected to www.googleapis.com (10.90.29.1) port 443 (#0)
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: ALPN, offering http/1.1
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: successfully set certificate verify locations:
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info:   CAfile: none
  CApath: /etc/ssl/certs/
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: TLSv1.2 (OUT), TLS header, Certificate Status (22):
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: Unknown SSL protocol error in connection to www.googleapis.com:443
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] == cURL Info: Closing connection 0
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] CURL error, CURLcode= 35, SSL connect error
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] Curl Error: 35, POST https://www.googleapis.com/oauth2/v3/token
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] CVRFGoogleCloud::SendRequest() - Error: Error = 44038
1914 77a 08/01 18:28:27 ### [CloudTestTool.e] GetRootFolderStatus() - Error: Error = 44038


Cloud test Tool Error:

1914 77a 08/01 18:28:27 ###   == cURL Info: TLSv1.2 (OUT), TLS header, Certificate Status (22):
1914 77a 08/01 18:28:27 ###   == cURL Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
1914 77a 08/01 18:28:27 ###   == cURL Info: Unknown SSL protocol error in connection to www.googleapis.com:443
1914 77a 08/01 18:28:27 ###   == cURL Info: Closing connection 0
1914 77a 08/01 18:28:27 ###   CURL error, CURLcode= 35, SSL connect error
1914 77a 08/01 18:28:27 ###   CVRESTBaseRemoteFile::SetRESTErrorCode() - Error: Error = 44038
1914 77a 08/01 18:28:27 ###   CVRFGoogleCloud::SendRequest() - Error: Error = 44038
1914 77a 08/01 18:28:27 ###   GetRootFolderStatus() - Error: Error = 44038
 

icon

Best answer by IS_CV 2 August 2022, 14:50

View original

5 replies

Userlevel 7
Badge +23

Check with your network admins.  Looks like port 443 might be blocked.

I only found 1 single case with this error, and the customer closed it themselves saying they had internal network issues.

Badge +2

Hi @Mike Struening 

We are able to do telnet to googleapis on port 443. there is no issue in that here.

Seems some SSL certificate issue but i am not sure.

Userlevel 7
Badge +23

Could be….I would suggest opening a support case so they could do a deeper check.  These are tough to troubleshoot outside the obvious port checks; much better to have an engineer dive in deep 🤓

Once you do, share the case number here.

Badge +2

Hii @Mike Struening ,

 

Issue is resolved. The URLs are not allowed in the firewall so that was causing the issue

Userlevel 7
Badge +23

Thanks for sharing!  Your solution is much more detailed than the previous ‘network issues’ fix 😎

Reply