Backup S3 with different port, certificate error

[marcoaperez]

I am trying to use our NAS to backup en S3 format and it works.

I am using a different port, 8010, because I cannot open port 443. I have checked from the servers with OTTO that it can access the 8010 port.

When I try to configure the offsite in OTTO this is the error message:

Can't connect
Connection failed! Unable to list buckets, please supply a bucket name and remote path to verify access: error listing: RequestError: send request failed caused by: Get "https://mynas:8010/": tls: failed to verify certificate: x509: certificate signed by unknown authority

If I connect with a browser and check the certificate is correct

If a go to terminal where Otto is installed I can check the open port

nc -vz mynas 8010
Connection to mynas (#.#.#.#) 8010 port [tcp/*] succeeded!

[kduval]

Hey Marco,

Are you using a self-signed cert? OttoFMS and RClone (which we use under the hood for S3 transfers) don’t support self-signed certs out of the box. OttoFMS does not have a workaround for this, and RClone’s workaround would require some significant changes to how OttoFMS’ offsites work.

You could maybe make this work using a reverse Proxy like Caddy or NGINX, but OttoFMS cannot do this natively.

-Kyle

[marcoaperez]

It is a certificate from QNAP, myqnapcloud.com