After installing Syncplify.me Server! v4.0 you will be able to manage it securely via web interface over HTTPS.
Now, a very common choice is to use a self-signed certificate, because it saves money and if you know what you’re doing it doesn’t compromise security. This is, in fact, the default choice offered by the HTTP/REST Configuration Wizard, and the most common choice among Chief Technology Officers (according to our surveys).
But if you use a self-signed certificate, your browser will warn you that your connection may not be private or secure. That’s because self-signed certificates are often used for man-in-the-middle (MITM) attacks. But this is not the case, of course, because in this case this particular self-signed certificate was created by you and for you.
To get rid of this annoying message, you basically have 2 options:
- Spend some money to buy a trusted X.509 (SSL/TLS) certificate from a Certification Authority like DigiCert, Comodo, Thawte, and the like.
- Simply accept the self-signed certificate you have just created and add it to the trusted keychain of your browser.
If you have chosen option #2, here’s how you do it in Chrome:
This is how you do it in Firefox:
And this is how you do it in Microsoft Edge (Internet Explorer behaves similar to this):
Once you do that, you will be able to securely access Syncplify.me Server!’s web management interface
