Search docs.molo17.com
    Operational guide Deploy and run

    Install and run Gluesync on Windows Server

    This guide takes a clean Windows Server from "nothing installed" to a healthy Gluesync Control Plane. It shows which installer to use, which folders and processes your antivirus or EDR must leave alone, how to start and stop Gluesync with Gluesync Control, how to update a server that has no internet access, and how to collect a support bundle when you need help.

    In this guide

    You will learn how to check the server before you install, choose between the Windows setup wizard and the PowerShell installer, add antivirus and EDR exclusions, install Gluesync, sign in to the Control Plane, start, stop and check Gluesync with Gluesync Control, update it from an offline package, and collect a support bundle.

    Quick information

    Goal

    Install Gluesync on Windows Server, keep it running, and know how to update it and get support

    Audience

    Windows Server administrators and the people who install Gluesync

    Level

    Intermediate

    Time required

    About 45 minutes, plus a server restart (the install itself takes 10 to 20 minutes)

    Area

    Windows Server → installer → Gluesync Control Plane

    Applies to

    Gluesync 2.3

    Before you begin

    Make sure that:

    1. You can sign in to the server with a local administrator account, and you can open PowerShell with Run as administrator;

    2. The server is a Windows Server (Windows 10 and 11 and other client editions are refused) and meets the table below;

    3. You have your kit ID, the 12 characters (0-9 and a-f) from the Gluesync download e-mail;

    4. The server can reach the internet for an online install, or you have the offline files described in Update Gluesync, also without internet access;

    5. If the server runs antivirus or EDR software, you can ask the team that manages it for the exclusions in Add the antivirus and EDR exclusions.

    Requirement What the installer checks

    Free disk space

    At least 100 GB free on the system drive, on the drive that holds Docker’s data folder and on the drive of the install folder. This is a hard block (GS-PRE-050) that no option overrides. The installer counts decimal gigabytes (100 billion bytes). Windows Explorer shows binary gigabytes, so 100 GB in the installer is about 93 GB in Explorer.

    Memory

    8 GB is the documented minimum. Below it the checker warns (GS-PRE-052); far below it the installation stops (GS-PRE-051).

    Processor

    4 cores or more. The setup wizard shows fewer cores as a recommendation. The PowerShell installer refuses to start with fewer than 4 cores (see Or install with the PowerShell installer).

    Windows version

    Windows Server 2022 or 2025. Windows Server 2019 is deprecated and cannot use the offline packages. Windows Server 2016 and the Semi-Annual Channel releases are blocked (GS-PRE-021). See System requirements.

    Windows containers

    Gluesync runs in native Windows containers with process isolation, using the Docker Engine that the installer installs for you. Docker Desktop must not be installed (GS-PRE-001). The installer turns on the Containers feature and restarts the server once.

    Ports

    Ports 80 and 443 must be free (GS-PRE-040), for example IIS must not use them.

    The screenshots and outputs in this guide come from a clean Windows Server 2022 Datacenter with 8 GB of memory, installed from a Gluesync kit.

    Which installer do I use?

    Start from the table. Use the Windows setup wizard unless one of the other rows describes your server.

    Question Setup wizard (gluesync-windows-setup-wizard.msi) PowerShell installer (docker-installer-windows.ps1) Legacy MSI (gluesync-platform-installer.msi)

    Use it when

    New installations on a server with a desktop. This is the default.

    Windows Server Core, remote or scripted installs.

    Only to repeat an existing deployment. It is frozen and replaced by the setup wizard.

    Needs a desktop session

    Yes for the guided install. It also runs silently with msiexec /qn.

    No. It runs in a PowerShell console, on Server Core too.

    Not covered by this guide.

    Works when Group Policy blocks PowerShell scripts (AllSigned, AppLocker, WDAC)

    Yes. It runs no PowerShell or VBScript at install time.

    No.

    No: it stops with GS-PRE-070.

    Installs Gluesync Control and the gluesync command

    Yes. The gluesync command is on the system PATH, and a Gluesync Control shortcut is created.

    No. In the lab the folder had the kit scripts run.ps1, stop.ps1, update.ps1 and collect-logs.ps1, and no gluesync command. To get Gluesync Control, run the setup wizard on the same server afterwards.

    Not covered by this guide.

    Offline install

    Yes: choose From files on this server.

    Use the separate offline script docker-installer-windows-offline.ps1.

    Not covered by this guide.

    Minimum processor

    Warns below 4 cores.

    Stops below 4 cores.

    Not covered by this guide.

    After the restart

    Resumes by itself as SYSTEM. Nobody needs to sign in. The launch window opens at the next sign-in.

    Resumes only when an administrator signs in, in a console that asks again for the kit ID.

    Not covered by this guide.

    In short:

    An installer sends anonymous install data to MOLO17 unless you turn it off: set GLUESYNCTELEMETRY=0 on msiexec, or run the PowerShell installer with -NoTelemetry. See Anonymous install data. The steps below turn it off.

    Guide steps

    Check the server before you install

    PowerShell

    1. Open PowerShell with Run as administrator;

    2. Download the signed pre-flight checker, gluesync-preflight.ps1, from the latest release of the Gluesync pre-flight checker project. The direct link is https://gitlab.com/molo17-public/gluesync/gluesync-pre-flight-checker/-/releases/permalink/latest/downloads/gluesync-preflight.ps1;

    3. Run it with your kit ID. The script changes nothing on the server:

      powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\gluesync-preflight.ps1 -KitId <kit id>

    4. Read each finding. A line that starts with [FAILED] blocks the installation and a line that starts with [WARNING] does not.

    Expected result

    On a server that Microsoft Defender scans, you see one warning and the result warn with exit code 0:

    [WARNING] GS-PRE-082 DEFENDER_NO_DOCKER_EXCLUSIONS: Microsoft Defender real-time protection scans Docker's data folder; ...
Preflight result: warn; exit code 0.

    The next step removes this warning. If you see [FAILED], fix it first: see Troubleshooting.

    Run the checker before you install, not afterwards. The container images use about 12 GB, so on a server that had only just over 100 GB free, the same check can report GS-PRE-050 (exit code 150) after a correct install. It is a check for installing, not a health check.
    Add the antivirus and EDR exclusions

    PowerShell

    Gluesync runs in Windows containers. In process isolation, every process in a container is also a process on the host, so security software can scan or end it. Docker also writes and renames thousands of files while it saves the images. Add these exclusions before you install, so the installation does not stop halfway and the containers do not restart in a loop.

    1. Find out whether Microsoft Defender scans files, or runs in passive mode because another product does:

      Get-MpComputerStatus | Select-Object AMRunningMode, RealTimeProtectionEnabled

    2. If AMRunningMode is Normal, exclude Docker’s data folder, the Gluesync folder and the Docker Engine process:

      Add-MpPreference -ExclusionPath "C:\ProgramData\docker"
Add-MpPreference -ExclusionPath "C:\Program Files\Gluesync"
Add-MpPreference -ExclusionProcess "dockerd.exe"

    3. Confirm what Defender now excludes:

      (Get-MpPreference).ExclusionPath
(Get-MpPreference).ExclusionProcess

    4. For any other antivirus or EDR product, ask the team that manages it to add the same folders and processes from the table below. A Defender exclusion has no effect on a third-party product. To find which products are installed, run fltmc and compare the filter names with Prepare antivirus and EDR software;

    5. Run the pre-flight checker again.

    Table 1. What to exclude, and why
    Exclude Kind Why

    C:\ProgramData\docker

    Folder

    Docker’s data folder. It holds the image layers (about 12 GB after the install) and the writable layer of every container. Scanning it makes Docker fail with failed to register layer …​ Access is denied.

    C:\Program Files\Gluesync

    Folder

    The install folder: the Compose file, the .env file, the Core Hub database and logs under data and logs, and Prometheus data. Gluesync reads and writes it all the time, so real-time scanning adds CPU and latency.

    dockerd.exe

    Process

    The Docker Engine. Exclude it, or trust it as an application in your EDR. For Defender Controlled folder access, allow C:\Program Files\Docker\dockerd.exe and docker.exe (GS-PRE-081).

    java.exe, node.exe, traefik.exe, prometheus.exe, grafana-server.exe, portainer.exe, CExecSvc.exe

    Processes inside the containers

    These are the processes that the running Gluesync containers show on the host. An EDR that ends them makes the containers show Restarting (3221226010). An exclusion for dockerd.exe alone does not cover them: add them as exceptions if your EDR blocks or ends them.

    C:\ProgramData\MOLO17\Gluesync and C:\GluesyncSupport\Logs

    Folders

    The installer state, installer logs, update backups and support bundles. With Defender Attack Surface Reduction rules in block mode, also exclude C:\Program Files\Docker*, C:\Program Files\Gluesync\* and C:\ProgramData\MOLO17\Gluesync\Installer\* (GS-PRE-080).
    Expected result

    Get-MpPreference lists both folders under ExclusionPath and dockerd.exe under ExclusionProcess, and the checker now ends with:

    Prerequisite checks passed (Windows build, RAM, disk, Docker Desktop, ports, network, antivirus).
Preflight result: pass; exit code 0.

    If Defender is managed centrally (Group Policy, Intune or Microsoft Defender for Endpoint), add the exclusions in that console. Central policy can ignore or replace the exclusions you add on the server.
    Install with the Windows setup wizard

    UI

    Follow this step when you chose the setup wizard. For the PowerShell installer, go to Or install with the PowerShell installer.

    1. Download gluesync-windows-setup-wizard.msi from molo17.com. The file is signed by MOLO17 SRL;

    2. Right-click the MSI and choose Run as administrator, or run msiexec /i gluesync-windows-setup-wizard.msi GLUESYNCTELEMETRY=0 from an elevated terminal to keep anonymous install data off;

    3. On Welcome to Gluesync platform setup, select Next;

    4. On License agreement, read the license, tick I accept the license terms and select Next;

    5. On Install folder, keep C:\Program Files\Gluesync\ and select Next;

    6. On System requirements, read every row, then select Next.

    System requirements page of the Gluesync platform setup with the check list marked by annotation 1 and the Next button marked by annotation 2
    Figure 1. The System requirements page shows one row for each check. Select Next when all required checks pass.

    1. On How do you want to install?, keep Download from MOLO17 and select Next. Choose From files on this server only for an offline install;

    How do you want to install page with Download from MOLO17 marked by annotation 1
    Figure 2. Choose where setup gets Gluesync. Download from MOLO17 needs internet access.

    1. On Your Gluesync kit, type your kit ID and select Next;

    Your Gluesync kit page with the Kit ID field marked by annotation 1 and the Next button marked by annotation 2
    Figure 3. Type the 12 characters of your kit ID. The ID shown here is the format example.

    1. On What happens next, select Next, then select Install on Ready to install;

    2. When Setup finished appears, select Finish. Windows asks you to restart the server. Select Yes.

    Restart message of the Gluesync platform setup with the Yes button marked by annotation 1
    Figure 4. Windows asks for a restart because the Containers feature was added. Select Yes.

    1. After the restart, setup continues by itself as SYSTEM, usually within about a minute. Nobody needs to sign in for this part. It installs Docker and the platform images;

    2. Sign in to the server. The Gluesync platform launch window opens and shows four stages: Checking Docker, Downloading platform images, Starting Gluesync services and Checking the services are running. Keep it open.

    Launch window with Gluesync is ready
    Figure 5. The launch window says "Gluesync is ready" and shows the address and the first sign-in.
    Expected result

    The launch window says Gluesync is ready and shows the address of the Control Plane (https://<server address>/), the user admin and the first password. Two shortcuts appear on the desktop: Gluesync Control Plane and Gluesync Control. C:\ProgramData\MOLO17\Gluesync\Installer\status.json shows "result": "Succeeded" with no warnings. In the lab, the install took about 10 minutes from Install to Gluesync is ready, including the restart.

    If you wait several minutes between Install and the restart, status.json can show "result": "Failed", error GS-RUN-040, and the message failure 1/3; the resume task retries this step in about 5 min. The Docker step cannot finish before the restart. Restart the server and setup continues: in the lab it then succeeded without any other action. Restart promptly, because the installer gives up after three failures.
    Or install with the PowerShell installer

    PowerShell

    Follow this step on Windows Server Core or for a scripted install, instead of the setup wizard.

    1. Open Installation kits & tools, validate your licence, select Windows Server and download docker-installer-windows.ps1. The script is signed by MOLO17 SRL;

    2. Make sure the server has 4 cores or more. With fewer, the script stops before it changes anything:

    PowerShell window with the line Detected 2 CPU cores. At least 4 are required marked by annotation 1
    Figure 6. With 2 cores the PowerShell installer stops at its own check, without a GS-PRE code.

    1. From an elevated PowerShell session, change to the download folder and run the script. Add -KitId to check your kit before anything is installed, and -NoTelemetry to turn off anonymous install data:

      powershell.exe -NoProfile -ExecutionPolicy Bypass -NoExit -File ".\docker-installer-windows.ps1" -KitId <kit id> -NoTelemetry

    2. Type yes to confirm. The script runs its checks, turns on the Containers feature and asks whether to restart;

    PowerShell window showing the restart question marked by annotation 1
    Figure 7. Type yes to restart. The script resumes by itself after you sign in.

    1. Type yes. After the restart, sign in as an administrator. The script opens a console again and continues;

    2. When asked Would you like to proceed with Gluesync setup? (y/N), type y;

    3. When asked Enter your kit ID, type your kit ID again. The script asks again after the restart even when you passed -KitId the first time;

    PowerShell window with the prompt Enter your kit ID marked by annotation 1
    Figure 8. After the restart, the script asks for the kit ID again.

    1. When asked Would you like to start Gluesync now? (y/N), type y. The script downloads the images and starts the containers.

    PowerShell window with the box GLUESYNC IS NOW RUNNING marked by annotation 1
    Figure 9. The script ends with a box that says GLUESYNC IS NOW RUNNING and shows the address.
    Expected result

    The console shows Gluesync started successfully! (7 running container(s) …​) and the address and first sign-in. In the lab, after the restart and the sign-in, the script took about 7 minutes to download the images and start Gluesync. Seven containers run. The script writes no status.json: its log is C:\ProgramData\MOLO17\Gluesync\Installer\logs\docker-gluesync-installation.log.

    This install has no gluesync command and no Gluesync Control. Manage Gluesync with the scripts in C:\Program Files\Gluesync: .\run.ps1, .\stop.ps1, .\update.ps1 and .\collect-logs.ps1, run from an elevated PowerShell. In the lab, .\stop.ps1 stopped all containers in 14 seconds and .\run.ps1 started the 7 containers again in 27 seconds. To get Gluesync Control and the commands in the next steps, run gluesync-windows-setup-wizard.msi on the same server. The rest of this guide assumes Gluesync Control.
    Sign in to the Control Plane

    UI

    1. Select Open Gluesync in the launch window, or the Gluesync Control Plane shortcut, or browse to https://<server address>/;

    2. The browser warns that the connection is not private, because the installer creates a self-signed certificate. Select Advanced, then Continue to localhost (unsafe). To remove the warning, install your own certificate: see Setup secure HTTPS and WSS with TLS;

    Browser warning Your connection isn’t private with the Continue to localhost link marked by annotation 1
    Figure 10. The self-signed certificate is not trusted by the browser. Continue to the site.

    1. Sign in with the user admin and the first password shown in the launch window;

    2. Create a new password when the page asks for one. It needs at least 8 characters, one lowercase letter, one uppercase letter, one symbol and one number;

    Create password page with the two password fields marked by annotations 1 and 2 and the Create password button marked by annotation 3
    Figure 11. The first sign-in forces a new password. Type it twice, then select Create password.

    1. Sign in again with admin and the new password.

    Gluesync Control Plane home page with the version label at the top left marked by annotation 1
    Figure 12. A healthy Control Plane after sign-in. The version is at the top left.
    Expected result

    The Control Plane opens on Welcome to Gluesync. If your database is reachable from this server, continue with Build your first pipeline. This guide stops here: the version at the top left is the release the kit installed, and the next steps keep it running and up to date.

    Start, stop and check Gluesync with Gluesync Control

    UI and PowerShell

    Open Gluesync Control from the desktop shortcut. It asks for administrator rights once.

    1. On the Overview tab, read the state at the top right (Running, Stopped, Starting or Docker not running), the version and the number of services;

    2. To stop Gluesync, select Stop, then Yes. Stop removes the containers and keeps your data;

    Gluesync Control Overview tab with the Running state marked by annotation 1 and the Stop button marked by annotation 2
    Figure 13. The Overview tab shows the state and the Start, Stop and Restart buttons.
    Stop Gluesync confirmation with the Yes button marked by annotation 1
    Figure 14. Stop asks for confirmation and says your data is kept.

    1. To start it again, select Start. You can do the same from an elevated terminal. Open a new terminal after the install, so that it sees the new PATH:

      gluesync status
gluesync stop
gluesync start
gluesync status --json
    Expected result

    After Stop, the window shows Gluesync is stopped and 0 of 7 running, and gluesync status prints Gluesync : Stopped and exits with code 3. After gluesync start (34 seconds in the lab) it prints Gluesync is running: https://<server address>, and gluesync status prints Services : 7 of 7 running and exits with code 0.

    Table 2. Gluesync Control commands
    Command What it does

    gluesync

    Opens the Gluesync Control window.

    gluesync start or gluesync run

    Starts Gluesync, pulling images only on the first start.

    gluesync stop

    Removes the containers and keeps volumes, images and data.

    gluesync restart

    Stops, then starts.

    gluesync status [--json]

    Prints the state, version and services. Exit code 0 means running, 3 means not running.

    gluesync update [--list | --dry-run | --package <file>]

    Updates Gluesync, see Update Gluesync, also without internet access.

    gluesync collect-logs

    Collects a support bundle, see Collect a support bundle.

    Do not use docker compose up, down or pull instead of these commands. They skip the checks that Gluesync Control runs.

    Run the command line from an elevated terminal. In a terminal that is not elevated, a command stops with GS-CTL-007 and exit code 740.
    Update Gluesync, also without internet access

    UI and PowerShell

    1. In the Gluesync Control window, open the Update tab. When the server can reach the internet, it offers the newest version in Update to. Select Update to <version> to update online;

    Gluesync Control Update tab with the version list and Update button marked by annotation 1 and the Update from file button marked by annotation 2
    Figure 15. The Update tab offers the newest version, and Update from file for a server with no internet.

    1. For a server with no internet access, download gluesync-update-windows-amd64-<version>.tar.gz on a computer that is connected, from Get Gluesync - offline downloads. The file is about 2.2 GB;

    2. Copy it to the server, for example to C:\Temp;

    3. Take a backup first if this is a production server: see Backup and restore. The Core Hub database migration is one-way;

    4. From an elevated terminal, check what the package would change. This changes nothing:

      gluesync update --dry-run --package C:\Temp\gluesync-update-windows-amd64-<version>.tar.gz

    5. Run the update. In the window, select Update from file…​ instead:

      gluesync update --package C:\Temp\gluesync-update-windows-amd64-<version>.tar.gz -y
    Expected result

    The dry run lists the images that change (Image changes (3)) and ends with Dry run: 3 image(s) would change; nothing was changed. The update prints five stages, [1/5] Checking the package and the installation…​ to [5/5] Checking the services are running…​, then Gluesync updated from <old version> to <new version>. and the folder with the backup of docker-compose.yml and .env. In the lab, moving from the 2.2 release line to Gluesync 2.3 from a 2.2 GB package took 5 minutes 18 seconds. You do not run gluesync start afterwards.

    Gluesync Control Plane home page after the update with the version label marked by annotation 1
    Figure 16. After the update, the Control Plane shows the new version at the top left.

    An offline package must be newer than the installed version. A package for the same or an older version is refused. If an agent you have installed has no image in the package, the update is blocked. See Offline installation and updates (Windows) and the GS-UPD codes in Installer error codes and troubleshooting.
    Collect a support bundle

    UI and PowerShell

    1. In Gluesync Control, open the Support tab;

    2. Leave Days of logs at 3 and Size limit (MB) at 1024, or change them;

    3. To keep the bundle on the server, tick Keep the bundle on this server only (do not upload). To send it to MOLO17, leave it unticked and type your Ticket number and the E-mail address of the ticket;

    4. Select Collect logs.

    Support tab with the keep-on-server checkbox marked by annotation 1
    Figure 17. Choose how many days of logs to collect, and whether to upload the bundle.

    1. The same from an elevated terminal:

      gluesync collect-logs --local-only
gluesync collect-logs --ticket <ID> --email <you>
    Support bundle is ready with the file
    Figure 18. The result shows the file, its size and how many files it holds.
    Expected result

    Support bundle is ready shows a file named gluesync-support-<date-time>.zip in C:\ProgramData\MOLO17\Gluesync\support. In the lab it was 171 kB and held 31 files. It contains the Gluesync and installer logs, the log of every container, docker ps, docker info, the Compose file and the other configuration files with passwords and tokens replaced by *, and a system snapshot. Attach it to your ticket on the support portal.

    Run gluesync collect-logs from an elevated terminal. Do not use the old collect-logs.ps1 of the kit without administrator rights: most of what it collects fails, and the zip it produces is almost empty.

    Verify the installation

    Verify the result

    You have successfully installed and are running Gluesync on Windows Server if:

    • The pre-flight checker ends with Preflight result: pass;

    • Defender (or your antivirus) lists C:\ProgramData\docker, C:\Program Files\Gluesync and dockerd.exe as exclusions;

    • gluesync status prints Services : 7 of 7 running and exits with code 0;

    • docker ps shows every container as Up, and none as Restarting;

    • You can sign in to the Control Plane with your own password;

    • gluesync collect-logs --local-only creates a bundle in C:\ProgramData\MOLO17\Gluesync\support.

    Troubleshooting

    Problem Possible cause What to do

    GS-PRE-050 LOW_DISK with exit code 150, although Explorer shows more than 93 GB free

    The installer counts decimal gigabytes. 100 GB is about 93 GB in Explorer, and the check uses the lowest free space of the system drive, Docker’s data folder and the install folder

    Free space on that drive, or move Docker’s data root (C:\ProgramData\docker\config\daemon.json) to a disk with 100 GB free. No option, -Accept or GLUESYNC_ACCEPT overrides this check.

    The PowerShell installer prints Detected 2 CPU core(s). At least 4 are required

    The script needs 4 cores. The setup wizard only warns

    Give the server 4 or more cores and run the script again. The pre-flight checker does not report this, so a pass there is not enough.

    Kit ID not valid in the wizard, or GS-PRE-030

    The ID does not have 12 characters from 0-9 and a-f

    Copy the ID again from the download e-mail. Spaces and capital letters are accepted.

    GS-PRE-031 KIT_NOT_FOUND

    The format is right, but the download server has no kit for that ID

    Check the ID against your download e-mail, or request the kit again at Get Gluesync.

    GS-PRE-082 warning, or GS-PRE-083 naming a product

    Defender scans Docker’s folders, or a third-party antivirus or EDR is installed

    Add the exclusions in Add the antivirus and EDR exclusions and run the checker again.

    GS-PRE-040 PORTS_IN_USE

    Port 80 or 443 is used by another program, for example IIS

    Stop that program or move its bindings, then run the installer again.

    GS-PRE-001

    Docker Desktop is installed

    Uninstall Docker Desktop, restart, and run the installer again.

    status.json shows Failed, GS-RUN-040, failure 1/3

    The resume task ran before the server was restarted

    Restart the server. Setup continues by itself. Check status.json again after the restart.

    The install stops after the restart with Access is denied while Docker saves the images

    A scanner holds Docker’s files open

    Add the exclusions in Add the antivirus and EDR exclusions, then follow Fix "Access is denied" when Docker downloads images on Windows Server.

    docker ps shows Restarting (3221226010)

    Security software ends processes inside the containers

    Add the exceptions for the container processes in Add the antivirus and EDR exclusions. See Containers keep restarting.

    Enabling the Containers feature fails with 0x80073701

    The Windows component store is damaged, for example after a half-applied update

    Restart, install all pending Windows updates and restart again, then run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, restart, run Install-WindowsFeature -Name Containers, restart, and run the Gluesync installer again. If Windows Update is blocked, run DISM with /Source:WIM:<media>\sources\install.wim:<index> /LimitAccess, using media of the same Windows build and language.

    gluesync is not recognized

    The terminal was opened before the install, or Gluesync was installed with the PowerShell installer

    Open a new elevated terminal. After a PowerShell install, use .\run.ps1 and .\stop.ps1, or run the setup wizard to add Gluesync Control.

    GS-CTL-007, exit code 740

    The terminal is not elevated

    Open PowerShell or Command Prompt with Run as administrator.

    gluesync update --package stops with a GS-UPD code

    The package is damaged, is for the installed or an older version, or the server is Windows Server 2019

    Copy the package again exactly as downloaded, check its size, and look up the code in Update codes (GS-UPD).

    The browser says the connection is not private

    The installer creates a self-signed certificate

    Continue to the site once, or install your own certificate: see Setup secure HTTPS and WSS with TLS.

    Related guides

    Contact MOLO17 Support if you need assistance with installing or running Gluesync on Windows Server, and attach the support bundle from the last step.