Page 1 of 2

Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 1:41 pm
by tiagocoelho2
Hello.

This behavior is old:
At times, the configuration pointing to the SSL certificate is changed to the path C:\ProgramData\Syncovery\Database, but as there are no certificates in this folder, the web page fails.
The certificate is located in "C:\Scripts\Certificados\Certificado xxxx.com.br"

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 2:04 pm
by tobias
Hi,
maybe it happens when the certificate expires?

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 3:10 pm
by tiagocoelho2
I'm not sure, but the certificate expires every 90 days. Approximately every 85 days, a new certificate is copied, but the Syncovery service is not restarted. Could this be the problem?
Is there any setting that can prevent this reconfiguration for the C:\ProgramData\Syncovery\Database folder?

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 3:42 pm
by tobias
I will check it. So you are using Syncovery 10 for Windows?

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 5:38 pm
by tobias
Hello,
Syncovery saves the certificate path with file name. Not the folder.

So if the new certificate's file name is different, and the old one expires, then the certificate configuration is cleared.

I will check if I can make Syncovery look for new certificates in the folder.

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 7:24 pm
by tiagocoelho2
Windows Server 2022.

The certificate always has the same name. The certificate is also used in other programs (for example, ftp server) and there are no problems.
Certificate name:

xxxx=domain name

C:\Scripts\Certificados\Certificado xxxx.com.br\xxxx.com.br-crt.pem
C:\Scripts\Certificados\Certificado xxxx.com.br\xxxx.com.br-key.pem

[WebServer]
StartWithScheduler=YES
Username=default
IP1=192.168.1.4
Port1=8999
Port1TLS=Y
EnforceTLS=Y
SSLCertFile=C:\Scripts\Certificados\Certificado xxxx.com.br\xxxx-crt.pem
SSLPrivateKeyFile=C:\Scripts\Certificados\Certificado xxxx.com.br\xxxx.com.br-key.pem
SSLCertPassword=xxxxxxxxxxxxxxxxxxxx
Port2TLS=N
IP2=192.168.1.4

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sat Apr 20, 2024 8:11 pm
by tobias
Hello,
OK, and what do you mean with "returns to C:\ProgramData\Syncovery\Database"?

Where do you see that?

And are you sure that only this path is shown without a file name?

If there is a file name, which name is it? The correct one or a different one?

What Syncovery may sometimes to is try to generate its own certificate if the existing one is too old.

But that doesn't seem to be the case here?

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sun Apr 21, 2024 10:25 am
by tiagocoelho2
Syncovery automatically changes the path defined to C:\ProgramData\Syncovery\Database\
When this happens I will post the result here.
Is there a log that I can activate so that this can be monitored?

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sun Apr 21, 2024 10:33 am
by tobias
Hello,
yes, there's a file called WebGUI.log in the folder
C:\ProgramData\Syncovery

Maybe you can send it to support@syncovery.com?

I am also working on an update today with several improvements in certificate handling, and more detailed logging to that file.

Re: Syncovery Web: Certificate configuration returns to C:\ProgramData\Syncovery\Database

Posted: Sun Apr 21, 2024 10:39 am
by tiagocoelho2
Looking at a test server and found the configuration changed;
Modou to
SSLCertFile=C:\ProgramData\Syncovery\Database\.xxxx.com.br-cert.pem
SSLPrivateKeyFile=C:\ProgramData\Syncovery\Database\.xxxx.com.br-key.pem

Note: also changed the file name from xxxx.com.br-cert.pem to .xxxx.com.br-cert.pem
Adding "." at the beginning of the file.

I will do 2 tests:
1. Redo a new configuration from scratch.
2. Enable existing configuration logging.