Install on macOS and FreeBSD

Both platforms use the same command line installer as Linux. It downloads the Connector, verifies its signature, installs it, registers it with the system service manager, starts it, and prints the setup wizard URL.

You need root, or sudo.

Use curl, not your browser

The macOS builds are not yet notarized by Apple. A file downloaded through a browser is tagged by macOS as quarantined and Gatekeeper will refuse to run it. A file downloaded with curl carries no such tag and runs normally, so the commands below fetch the archive rather than linking it.

Install on macOS

Apple silicon (M1 and later):

curl -fsSLO https://sc-release.us-ord-10.linodeobjects.com/sc-setup/latest/sc-setup-darwin-arm64.tar.gz
tar xzf sc-setup-darwin-arm64.tar.gz
sudo ./sc-setup install

Intel Macs:

curl -fsSLO https://sc-release.us-ord-10.linodeobjects.com/sc-setup/latest/sc-setup-darwin-amd64.tar.gz
tar xzf sc-setup-darwin-amd64.tar.gz
sudo ./sc-setup install

Run uname -m if you are not sure which you need: arm64 means Apple silicon, x86_64 means Intel.

Install on FreeBSD

fetch https://sc-release.us-ord-10.linodeobjects.com/sc-setup/latest/sc-setup-freebsd-amd64.tar.gz
tar xzf sc-setup-freebsd-amd64.tar.gz
sudo ./sc-setup install

What you extracted

The archive puts two files in the current directory:

File	What it is
sc-setup	The installer. Already executable, so there is no chmod step
sc-setup.sig	Its signature

Keep both files together

The installer verifies itself against sc-setup.sig before it touches anything, and refuses to run without it. Extract the whole archive into one folder and run sc-setup from there. Do not move or rename one file without the other.

The installer asks how the admin console should be reachable, then reports each step and finishes with the URL to open. For a headless machine, install with network access so you can finish the setup from your workstation:

sudo ./sc-setup install --access network

That binds 0.0.0.0:8883 over HTTPS with a self signed certificate. Your browser warns about that certificate once; that is expected.

Continue with First run.

What it installed

Thing	Where
The program	/usr/local/bin/sc-conn
The uninstaller	/usr/local/bin/sc-setup
The data directory	/opt/Syncplify/sc-conn
The service	A launchd job on macOS, an rc.d service on FreeBSD, enabled and started

Signature verification

Two separate checks happen, both against a release key built into the installer itself:

1. The installer verifies itself against sc-setup.sig before it does anything at all. This is step 1 of 8, and it is why the two extracted files have to stay together.
2. It then verifies the Connector package it downloads, before installing it.

That key is held offline by Syncplify. Neither the Portal nor your site holds it, so neither of them can distribute a Connector build, or an installer, that a machine would accept.

Every published file is listed in checksums.txt if you want to check a download before extracting it.

All the flags

The flags are identical to the Linux installer. See Install on Linux.

Managing the service

sudo sc-conn svc status
sudo sc-conn svc stop
sudo sc-conn svc start
sudo sc-conn svc restart

Updating

Do not re-run the installer to update. Updates have their own path, with a rollback slot and an automatic health check. See Updates.

Uninstalling

sudo sc-setup uninstall

The data directory is kept, so reinstalling picks up exactly where the Connector left off: same identity, same virtual file systems, same encryption keys, same enrollment.

To delete it as well:

sudo sc-setup uninstall --purge

--purge is permanent

It deletes your at rest encryption keys. Syncplify does not have them and cannot recover them. Any data still encrypted with them becomes permanently unreadable.