Cert error with 2.0.4.14 on OS X Mojave


#1

I upgraded to 2.0.4.14 today. Backups complete but throw certificate errors:

Installed certs via sudo -i & curl -O https://curl.haxx.se/ca/cacert.pem; cert-sync --user cacert.pem; rm cacert.pem

Mono Certificate Store Sync - version 5.18.0.0

Populate Mono certificate store from a concatenated list of certificates.

Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

Importing into legacy user store:

I already trust 128, your new list has 135

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R1

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R2

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R3

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R4

Certificate added: C=CN, O=UniTrust, CN=UCA Global G2 Root

Certificate added: C=CN, O=UniTrust, CN=UCA Extended Validation Root

Certificate added: C=FR, O=Dhimyotis, OU=0002 48146308100036, CN=Certigna Root CA

7 new root certificates were added to your trust store.

Import process completed.

Importing into BTLS user store:

I already trust 128, your new list has 135

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R1

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R2

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R3

Certificate added: C=US, O=Google Trust Services LLC, CN=GTS Root R4

Certificate added: C=CN, O=UniTrust, CN=UCA Global G2 Root

Certificate added: C=CN, O=UniTrust, CN=UCA Extended Validation Root

Certificate added: C=FR, O=Dhimyotis, OU=0002 48146308100036, CN=Certigna Root CA

7 new root certificates were added to your trust store.

Import process completed.

Running a backup still generates cert errors. Any thoughts?


#2

Hi @jv123, welcome to the forum!

Are you running Duplicati as a service / daemon? If so, this might help:
2.0.3.7 on Mac: Missing certificates


#3

Yeah, I had already run this while sudo’d to root, but it didn’t fix anything. However, I just re-ran it, from my user account and the errors are gone.

I guess certs are user-dependent.


#4

Yep - and the in-app message assumes running as root. :frowning:

Glad you got it working though!