# Duplicati failed to connect Amazone s3

**URL:** <https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568>\
**Category:** Uncategorized\
**Created:** [February 19, 2018, 1:51pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568 "2018-02-19T13:51:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sinsha](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/s/46a35a/32.png) [@Sinsha](https://forum.duplicati.com/u/Sinsha)\
**Post date:** [February 19, 2018, 1:51pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/1 "2018-02-19T13:51:30Z")

</div>

Hi,

I got below error while configuring connection Amazone s3:

Failed to connect: Invalid type System.Net.HttpWebRequest for instance field Amazon.Runtime.Internal.HttpRequest:\_request

---

<div class="post-metadata">

**Author:** ![Sinsha](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/s/46a35a/32.png) [@Sinsha](https://forum.duplicati.com/u/Sinsha)\
**Post date:** [February 19, 2018, 1:52pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/2 "2018-02-19T13:52:41Z")

</div>

This is happened Ubuntu 16.04  
Duplicati version : 2.0.2.1-1

---

<div class="post-metadata">

**Author:** ![Sinsha](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/s/46a35a/32.png) [@Sinsha](https://forum.duplicati.com/u/Sinsha)\
**Post date:** [February 20, 2018, 5:30am UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/3 "2018-02-20T05:30:56Z")

</div>

Not able to create backup/restore with Amazone s3

---

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [February 22, 2018, 9:08pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/4 "2018-02-22T21:08:57Z")

</div>

That’s strange as a lot of other people have had no issues with S3.

However, a search of the forum for `Amazon.Runtime.Internal.HttpRequest:_request` seems to indicate other users have run into the issue with S3 COMPATIBLE destinations (such as Minio).

In at least one case, the solution was to set the `--allowed-ssl-versions` to `TLS12` for the specific job (apparently it didn’t help when setting globally).

> [@Windows service + minio with ssl error](https://forum.duplicati.com/t/windows-service-minio-with-ssl-error/527/4):
>
> I figured this out, want to document it for the sake of others. Synopsis: When using Duplicati with a Windows service, have to specify TLS12 at the job level in order to work with Minio. Setting at a global level does not appear to take. It did automagically work when I was using it as a desktop application instead of a Windows service, but I probably won’t have time to reproduce with a new system to determine the difference. Details: I used ssldump on my minio server to capture packets. 1…

Can you try that out and see if it helps?

---

<div class="post-metadata">

**Author:** ![Sinsha](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/s/46a35a/32.png) [@Sinsha](https://forum.duplicati.com/u/Sinsha)\
**Post date:** [February 22, 2018, 9:47pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/5 "2018-02-22T21:47:57Z")

</div>

Thanks for reply back.

Somehow this was my software update issue in my system. ca-certificates-mono was not updated.

Below commands solved my issue

sudo apt get update  
sudo apt-get install ca-certificates-mono

---

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [February 22, 2018, 9:52pm UTC](https://forum.duplicati.com/t/duplicati-failed-to-connect-amazone-s3/2568/6 "2018-02-22T21:52:32Z")

</div>

Glad to hear you got it working!

The certificates issue with mono is not uncommon, though usually I think it has a different error attached to it or I might have suggested that fix sooner. 😊

(Oh, I went ahead and your post as the solution in case others get the same error.)
