Enterprise support
You ask MOLO17 for support in the support portal at support.molo17.com. The portal is available around the clock. For an incident, response times follow the SLA of your Enterprise agreement, not a generic inbox.
Portal access
| URL | support.molo17.com |
|---|---|
Hours |
24/7 access. Engineers respond against your SLA. |
Login |
Your own account. Sign in with your email and password, or with Google or Microsoft. To create an account, use your work email and verify it: the portal links the account to your company. For a whole team, each person creates their own account. |
Request types |
Bug, Help, Change and Incident. An Incident needs an Enterprise license. Without it, the portal opens the request as Help and keeps the priority you chose. |
Help from Spark |
Describe the problem on the Home page and Spark shows the documentation and similar solved cases, and suggests the request to open. Nothing is sent until you submit the form. |
Logs |
Every request has a log upload voucher. Core Hub and Gluesync Control use it to send a support bundle straight into the request. See Exporting / Uploading logs to support. |
Step-by-step guide with screenshots: Use the MOLO17 support portal. The short version, and the logs to attach for each kind of problem: How to create a support ticket.
SLA (incidents)
When you open an incident, these are the enterprise commitments by priority. "Resolution time" is a target for restoring service, not a guarantee that a code fix ships in that window.
| Priority | Meaning | Response | Resolution target |
|---|---|---|---|
P1 — Critical |
Service down or completely unusable |
Within 4 hours |
Within 8 hours |
P2 — High |
Service severely impaired |
Within 8 hours |
Not strictly defined |
P3 — Medium |
Service partially impaired |
Within 3 business days |
Not strictly defined |
Versioning and lifecycle
Gluesync versions look like a.b.c.d (for example 2.1.10.6).
| Segment | Meaning |
|---|---|
|
Product family. |
|
Major release of that family, typically every 6–8 months. Can add capabilities and, when unavoidable, breaking changes. |
|
Feature release. New functionality, no breaking changes. Typically about every two weeks. |
|
Hotfix. Fixes and patches. Issued as needed, sometimes daily. |
Each a.b line has two dates, counted from that line’s first release:
| Milestone | Meaning | When |
|---|---|---|
End of Fix (EoF) |
No further patches on that line. Move to the current line — upgrades are covered by the subscription. Critical security fixes after EoF are only by special agreement. |
1 year after release |
End of Support (EoS) |
No further product support on that line. |
2 years after release (1 year after EoF) |
Need cover past EoS? sales@molo17.com for extended-support options.
There is no Gluesync 3.x plan today. If a future family appears, the same EoF / EoS clock would apply.
Current lines
| Line | First release | End of Fix | End of Support |
|---|---|---|---|
2.3 |
October 13, 2026 |
October 13, 2027 |
October 13, 2028 |
2.2 |
March 5, 2026 |
March 5, 2027 |
March 5, 2028 |
2.1 |
June 27, 2025 |
June 27, 2026 (passed) |
June 27, 2027 |
The last 2.1 patch was 2.1.11.4 on March 3, 2026. 2.1 is past End of Fix: no further patches, support until End of Support only, with critical security fixes by special agreement.
2.3 first shipped on October 13, 2026. End of Fix is October 13, 2027, and End of Support is October 13, 2028. See What’s new in 2.3 and Deploy and run.
Security updates and CVE patch cycle
Base image and dependency updates follow a quarterly image refresh cycle. This covers OS packages in the container images, bundled runtimes (for example the Node.js runtime in Conductor and the Azul Zulu JDK in Core Hub) and third-party images shipped with Gluesync.
Critical vulnerabilities are assessed case by case and may be patched outside that cycle. To ask about a specific CVE, open a ticket in the support portal.
For how MOLO17 scans and fixes vulnerabilities in the images, see Security statement and vulnerability handling.
Exporting / Uploading logs to support
Support will often ask for logs. Always send a compressed archive, never raw .log files.
For a step-by-step walkthrough, see the how-to guide Read Gluesync logs and diagnose errors.
The simplest way is the voucher of your ticket: Core Hub and Gluesync Control upload the logs straight into the ticket, with nothing to attach by hand.
Your ticket voucher
Every support ticket gets a voucher, a code in the form GSV-XXXX-XXXX-XXXX. You find it in two places:
-
on the ticket page in the support portal;
-
in the e-mail you receive when the ticket is opened.
With the voucher, a log bundle goes into the ticket as an attachment, with a comment from the Support Bot that names the product, the version, the host and the size. You do not need the ticket number or an e-mail address.
-
The voucher is valid while the ticket is open and for 30 days after it is closed. If the ticket is reopened, it works again.
-
You can type it in lower case, with or without the dashes and the
GSVprefix:gsv-ab12-cd34-ef56andab12cd34ef56are the same voucher. -
A bundle can be up to 5 GB. It is sent in resumable parts of 16 MB, and its size is checked when the upload ends. A part that fails is sent again, not the whole bundle.
-
If you lose the voucher, open the ticket in the portal: it is shown there. Support can also issue a new one.
-
Treat it like a password for the ticket: it lets whoever has it add files to that ticket, and nothing else.
Network access
The host that uploads needs outbound HTTPS (port 443) to two destinations. Both are needed: the first starts and completes the upload, the second receives the bytes.
| Purpose | Address |
|---|---|
Support portal API |
|
Upload storage |
|
Core Hub and Gluesync Control use the proxy settings of the host; Conductor uses its PROXY_HTTPS (or PROXY_HTTP) setting. To send the upload to another API address, set the environment variable GLUESYNC_SUPPORT_API_URL on the host that runs the upload.
Core Hub (recommended)
Prefer the Core Hub UI when you have it. Open Settings → Support and scroll to Log collection for support.
Upload Logs to Support and gluesync collect-logs accept the voucher of your request, a code like GSV-XXXX-XXXX-XXXX. Copy it from the LOG UPLOAD VOUCHER card on the request page of the support portal (see Use the MOLO17 support portal) and give it to the tool, with --voucher <code> on the command line. Older versions ask for the email and the ticket ID instead, as described below.
Export & upload logs to support (needs internet access):
-
Enter the voucher of your ticket in Support voucher, for example
GSV-AB12-CD34-EF56. A code with the wrong shape is refused in the form, before anything is sent. -
Click Upload Logs to Support. Core Hub checks the voucher, archives its logs and uploads the archive to the ticket.
-
When the upload ends, the result shows the ticket, the size of the archive and whether the size was verified.
Collect full environment logs, statistics and metrics appears only when an external module such as Conductor is connected. Select it when support needs logs beyond Core Hub, for example from external modules. The button then becomes Collect & Upload Logs. Collection can take several minutes and may temporarily use extra disk space while the logs are redacted.
With Collect full environment logs, statistics and metrics, Conductor collects the logs and uploads the archive to the ticket with the same voucher. Conductor 0.14.0 and earlier do not take a voucher: the form then says so. Update Conductor, or use Legacy: ticket number and e-mail, see Ticket number and e-mail (legacy).
If the upload fails, the message says why:
| Problem | What to do |
|---|---|
The voucher is not valid |
Check the code against the ticket page. A voucher that support revoked, or a code that does not exist, gives the same answer. Ask support for a new one. |
The voucher has expired |
The ticket was closed more than 30 days ago. Open a new ticket, or ask support to reopen it. |
The archive is larger than 5 GB |
Nothing is uploaded. Collect fewer days of logs, or send the archive in another way (see Get a local archive to MOLO17). |
Too many requests |
Wait and try again. After several wrong vouchers in an hour, the host is blocked for an hour. |
The support portal cannot be reached |
Check the firewall and the proxy: see Network access. |
No external internet access? Use local logs collection:
-
Optionally select Include database to add an archive of the Core Hub database.
-
Click Collect Local. No voucher is needed.
-
When Archive created: appears, click the archive name to download it.
Attach the downloaded archive to the ticket in the support portal. Over a remote tunnel, very large archives can fail to download; in that case copy the archive from the host (see Copy an archive from a remote host).
Details: Collect and send logs to MOLO17 support.
| How to send logs, next to the section title, opens a help dialog with the platform-specific steps. |
Ticket number and e-mail (legacy)
The form still accepts the ticket number and the e-mail address you opened the ticket with, instead of a voucher, for a transition period. Click Legacy: ticket number and e-mail under the voucher field, enter the Email and the Ticket number (for example GSSD-123), and click Upload Logs to Support. Use a voucher instead goes back to the voucher field. Core Hub then uploads the archive over WebDAV to webdav.molo17.com. It no longer falls back to FTP and no longer uses curl. A voucher and a ticket number cannot be sent together: use one or the other.
Linux kit collector
The default installation path for Gluesync in Linux is /opt/gluesync. The Linux installer (installer 2.0, Gluesync Control 1.4.5) puts Gluesync Control for Linux on the PATH. Run, from any folder:
sudo gluesync collect-logs --voucher GSV-XXXX-XXXX-XXXX
Add --local-only to keep the bundle on the server: the command prints the path of the zip file, in /var/lib/gluesync/support.
The ticket number and the e-mail address still work as a legacy option: sudo gluesync collect-logs --ticket <ID> --email <you>.
Installations made with an earlier installer or kit also have collect-logs.sh. Run it inside the gluesync-docker directory:
./collect-logs.sh
macOS kit collector
Run the collector inside the gluesync-docker directory from the kit received by email:
./collect-logs.sh
Windows kit collector
Windows setup wizard 1.4.0 and later installs Gluesync Control. Open Command Prompt or PowerShell as administrator and run:
gluesync collect-logs --voucher GSV-XXXX-XXXX-XXXX
Or open the Gluesync Control shortcut on the desktop, go to the Support tab, enter the voucher, and click Collect logs. Add --local-only to keep the bundle on the server: the command prints the path of the zip file in %ProgramData%\MOLO17\Gluesync\support.
The ticket number and the e-mail address still work as a legacy option: gluesync collect-logs --ticket <ID> --email <you>, and the Support tab has a field for each.
Installs made before setup wizard 1.4.0 keep the PowerShell collector. The default installation path for Gluesync on Windows is C:\Program Files\Gluesync. In PowerShell, run the collector inside the gluesync-docker-windows directory:
.\collect-logs.ps1
Collector behaviour
gluesync collect-logs does not prompt: give --voucher to upload, or --local-only to keep the bundle. The upload checks the voucher before it collects anything, so a wrong or expired voucher stops at once. When the upload ends, the command deletes the local bundle only if you gave --delete-after-upload and the size held by the support portal matches the size of the bundle.
The kit scripts collect-logs.sh and collect-logs.ps1 are the legacy collectors: they ask for the email used to open the ticket and the ticket ID so they can upload. Press Enter twice to skip both prompts and keep a local support-logs.zip or support-logs.tar.gz; the script prints the local path of the archive.
If the collector is missing from your kit, open Installation kits & tools, validate your licence, select the host operating system, and download collect-logs.sh, or collect-logs.ps1 for a Windows install made before setup wizard 1.4.0. On Linux (Gluesync Control 1.4.5 installer) and on Windows Server (setup wizard 1.4.0 or later), you have gluesync collect-logs.
Get a local archive to MOLO17
When the upload fails, or the host is offline, keep the bundle on the server (--local-only, Collect Local, or an offline collector run), then attach the archive to your ticket in the support portal or in a ticket reply. The ticket web folder at https://ftp.molo17.com/ remains as a legacy option.
Copy an archive from a remote host
On Linux or macOS:
scp user@host:/path/support-logs.tar.gz .
From Windows, use WinSCP or PuTTY’s pscp:
pscp user@host:/path/support-logs.tar.gz .
Manual collection
If you do not have the collector scripts, run one of these commands from the Gluesync installation directory.
With zip:
find . -type f -name "*.log" -print0 | xargs -0 zip support-logs.zip
If zip is unavailable:
find . -type f -name "*.log" -print0 | xargs -0 tar -czvf support-logs.tar.gz
On Windows PowerShell:
$logs = Get-ChildItem -Recurse -Filter *.log; Compress-Archive -Path $logs.FullName -DestinationPath support-logs.zip
Docker & Kubernetes (for advanced users)
Docker Compose:
docker compose ps
docker compose logs --tail=500 -t > gluesync-logs.txt
docker compose logs gluesync-core-hub > gluesync-core-hub-logs.txt
Kubernetes (repeat for each relevant pod, then compress before sending):
kubectl logs <pod> -n <namespace> --all-containers > gluesync-logs.txt
Compress gluesync-logs.txt (or the collected files) before sending them to MOLO17.