Cannot retrive certificate from S3 Cloudian

[mciacci79]

Hello, In our hosted provider we have a S3 cloudian connected to Veeam (10a), many times we get this error "Failed to retrive certificate from : https:xxxxx" This appliance use self-signed certificate and for a scaleout repo support suggest add to add this key to register SOBRArchiveS3DisableTLS to 1 and seems to works, but now we have a FileShare backup that not use S3 via SOBR, but directly from the job, is it possibile disable SSL at all for this? or anyway there a other solution? like install certificate or somethings?we can't install a regular certificate to cloudian because is hosted thanks all!

We have opened a SR # 04377890

[Dima P.]

Hello Marco,

Thank you for your post. Checking your case details, stay tuned.

[mciacci79]

Any news?
i've found this error during restore

Code: Select all

[18.11.2020 15:02:22.931] < 51916> cli| Network.RetrieveSslCertificate
[18.11.2020 15:02:22.931] < 51916> cli|   (EString) HostName = s3-cloudian.xxxxxxxxxxxx
[18.11.2020 15:02:22.931] < 51916> cli|   (EInt32) Port = 443
[18.11.2020 15:02:22.931] < 51916> cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[18.11.2020 15:02:22.931] < 51916> net| Retrieving certificate for s3-cloudian.xxxxxxxxx:443
[18.11.2020 15:02:43.943] < 51916> net| Retrieving certificate for s3-cloudian.xxxxxxxxx:443 Failed.
[18.11.2020 15:02:43.944] < 51916> cli| ERR |Failed to process {Invoke} command
[18.11.2020 15:02:43.944] < 51916> cli| >>  |Details:
[18.11.2020 15:02:43.944] < 51916> cli| >>  |connect: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[18.11.2020 15:02:43.944] < 51916> cli| >>  |Agent failed to process method {Network.RetrieveSslCertificate}.

A strange timeout, Cloudian is in the same vlan of Veeam server, no firewalling between

regards

[Dima P.]

Hello Marco,

We do not have similar key for NAS backup functionality, but still discussing your case with RnD folks. I'll update this thread with the results of our findings, meanwhile please keep working with the support team. Cheers!

[Dima P.]

Marco,

Looks like the original case related to scale-out backup repository was closed and log are now removed. Can you please raise another ticket related to nas archive repository and share the case ID with me? Thank you in advance!