Error: Join. Exception: Windows Azure Storage exception: The SSL connection could not be established, see inner exception

GroupDocs.Merger Cloud Product Family
1

Hi,
I found many failed requests since yesterday (first bad request: “Request Start Date
2024-04-18 8:41:35 PM” (https://dashboard.groupdocs.cloud/billing/api-usage)

Error: “Join. Exception: Windows Azure Storage exception: The SSL connection could not be established, see inner exception…”

I can connect to Azure Storage using Azure Storage Explorer and also your storage viewer in https://dashboard.groupdocs.cloud/files
I verified all files requested for merge are in Azure Storage. I can connect and download these documents from Azure Storage.

Please give me some help.
Zbigniew Lapinski

2

Hi, @Zbyloo ! We are ready to help you. Please confirm, the issue is still persist? What message do you get? Please share your request/SDK code, and custom storage settings (without secret keys).

3

Hi Sergei,
Yes problem is still here.
Today I also created new Azure Storage Account and error is the same: I can connect, view, upload, download files to/from Azure Storage using GroupDocs Dashbord: https://dashboard.groupdocs.cloud/files
Trying to run any required storage access endpoint from your Swagger (GroupDocs.Merger for Cloud - API References) return 502 error (eg: ‘https://api.groupdocs.cloud/v1.0/merger/storage/exist/%2FTest%20PDF.pdf?storageName=AzureLqs’). API usage Logs (https://dashboard.groupdocs.cloud/billing/api-usage) shows ERROR: “Error: ObjectExists. Exception: Windows Azure Storage exception: The SSL connection could not be established, see inner exception…”.
Aplication id: 7d4a04b9-536a-47cd-8d32-25a911891cae

4

@Zbyloo
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): MERGERCLOUD-83
5

Hi, @Zbyloo, sorry for delayed answer, please confirm that issue still persists. I have tested GroupDocs.Merger Cloud with Azure storage and found no issues. Please ensure that you have selected “Default HTTPS endpoing” in the connection settings of Azure storage at dashboard and try again.