Updates

System, then Updates.

Updates are applied only when you decide. Nothing is installed behind your back.

What an update does

1. The Connector service stops.
2. The binary is swapped, keeping the previous version in a rollback slot.
3. The service restarts.
4. A health check runs. If it fails, the previous version is restored automatically.

Live user sessions reconnect. Transfers in progress are interrupted, so do it in a quiet moment.

Checking for one

The page shows your running version and your release channel, and tells you when it last looked.

The Connector checks once a day on its own. It only ever looks; nothing is downloaded or installed by that check. Your Portal also relays offers, and a banner appears on the dashboard when a version is available. Check now asks the channel immediately.

You never have to type a channel URL. The Connector ships knowing where releases live and reads its signed channel on its own. The Private release repository box at the bottom of the page is for large customers for whom Syncplify has set up a repository of their own, a paid option; leave it blank otherwise.

For the daily check and the download to work, the Connector needs outbound HTTPS to the release channel host. See Network requirements, and System, then Network, which lists every destination this Connector needs, the channel host among them.

Applying one

Apply update becomes available as soon as a newer version is known, and names the version it will install, for example Apply update (1.0.3). If it is greyed out, this Connector is already running the current version.

You are asked to confirm twice, on purpose: the second confirmation is the moment of service interruption.

The page reconnects on its own once the service is back, and reports the version it is running.

If the update fails its health check, the page says it was rolled back to the previous version.

From the command line

sc-conn update status
sc-conn update check
sc-conn update apply
sc-conn update rollback

Signature verification

Every update package is verified against a release key built into the Connector binary itself before anything is applied.

That key is held offline by Syncplify. Neither the Portal nor your site holds it, so neither of them can distribute an update a Connector would accept, however compromised they were.

Containers never update themselves

A Connector running in a container detects that, and its Updates page becomes informational: it reports version skew and applies nothing.

The image is the unit of deployment. Update by rerolling the image to the new tag, exactly as with any other container. See Run in Docker.

Not the installer

Do not re-run sc-setup to update. The installer's job is the first install; updates have the rollback slot and the health check, and the installer does not.

Version skew with your site

The Connector and your site are updated independently and are designed to interoperate across versions, so the order does not matter.

Two things do:

• A Connector far behind may be missing a feature the Portal offers. The Portal tells you when a Connector is too old for an operation, for example an automatic move to a dedicated server.
• Security critical updates can be pushed with notice over a manual policy. You will hear about it first.