Search docs.molo17.com

    Gluesync conductor screenshot Conductor error codes

    When a Conductor request fails, Conductor works out why and answers with a diagnosis: a code, who has to act, and the steps to take. This page lists every code. Support will ask you for the code, so copy it from the reply or from the Core Hub UI.

    Where you see a code

    Conductor puts the diagnosis in these places:

    • The error reply of a request that depends on the MOLO17 services (for example an update or a version check) has a diagnosis object next to success, error and details.

    • The error reply of a request that failed on the files of this installation has one too: DISK_FULL (HTTP 507) and COMPOSE_FILE_CORRUPT (HTTP 500).

    • GET /connectivity runs the same checks on demand and returns the diagnosis as data. It always answers HTTP 200, because the finding is the result, not an error. When everything is fine the code is CONNECTIVITY_OK.

    • The Core Hub UI shows the code, who has to act and what to do, in its own words.

    The diagnosis object has these fields:

    Field Content

    schemaVersion

    Version of the diagnosis format. It is 1.

    code

    One of the codes on this page.

    owner

    Who has to act. See Who acts.

    confidence

    How sure Conductor is: high, medium or low.

    params

    The values the meaning of the code refers to, for example the host name or the file path. The names are listed per code below.

    resolutionCodes

    The steps to take, as codes. See Resolution codes.

    fallback

    English title, summary and steps for the code, for logs, for curl and for clients that do not know the code.

    checks

    The connectivity checks that ran. Each has an id (proxy, internet-ip, internet-name, backoffice, status-feed or registry), ok, and, when available, ms and detail.

    source

    The service that produced it: gluesync-conductor.

    at

    When the diagnosis was made, as an ISO 8601 date and time.

    Codes are never renamed or reused. A new Conductor version can add codes, so a client must show fallback for a code it does not know.

    Who acts

    The owner field tells you where the problem is.

    owner Who acts Meaning

    customer

    Your environment

    The network, proxy, firewall, DNS or disk of the host that runs Gluesync. MOLO17 cannot fix it from outside.

    molo17

    MOLO17 services

    The MOLO17 update service has a problem. Nothing needs to change on your system.

    local

    This installation

    Conductor, Docker, Core Hub or the Conductor files on this host.

    unknown

    Unknown

    The checks did not find a single cause. Send the details to support.

    none

    Nobody

    Nothing is wrong.

    Error codes

    The HTTP status is the one Conductor uses when the code is the reason a request failed. In the Meaning column, a value in angle brackets, such as <host>, is a value from params.

    Code HTTP status Who acts Meaning What to do

    CONNECTIVITY_OK

    200

    Nobody (none)

    All connectivity checks passed. This host can reach the MOLO17 services it needs. Returned by GET /connectivity.

    Nothing to do.

    TRANSIENT_FAILURE

    502

    Unknown (unknown)

    A request failed but the services are reachable now. The request failed (<errorKind>), but every connectivity check passes now. This is usually a temporary network interruption.

    Params: errorKind.

    1. Wait a few minutes and try again.

    2. Contact MOLO17 support and attach the technical details.

    CONDUCTOR_UPDATING

    503

    This installation (local)

    Conductor is updating. Conductor is applying an update and temporarily refuses requests.

    Wait for the Conductor update to finish. The page recovers on its own.

    DOCKER_NOT_READY

    503

    This installation (local)

    Docker is not ready yet. Conductor cannot reach the Docker daemon yet. This is common right after a restart.

    1. Wait a few minutes and try again.

    2. Make sure the Docker service is running on this host.

    COREHUB_UNAVAILABLE

    503

    This installation (local)

    Core Hub is not responding. Conductor could not verify your session with Core Hub.

    1. Wait a few minutes and try again.

    2. Make sure the Core Hub service is running.

    PROXY_UNREACHABLE

    502

    Your environment (customer)

    The configured proxy cannot be reached. Conductor cannot open a connection to the proxy <host>:<port>.

    Params: host, port.

    1. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    2. Contact MOLO17 support and attach the technical details.

    PROXY_AUTH_REQUIRED

    502

    Your environment (customer)

    The proxy requires valid credentials. The proxy rejected the request with HTTP 407.

    1. Verify the proxy username and password in PROXY_HTTPS / PROXY_HTTP.

    2. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    NO_INTERNET

    502

    Your environment (customer)

    This host has no internet access. Neither the connection by address nor the one by name could be established.

    Params: viaProxy.

    1. Check this host’s network connection and default gateway.

    2. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    DNS_FAILURE

    502

    Your environment (customer)

    Host names cannot be resolved. This host reaches the internet by address but cannot resolve <host>.

    Params: host.

    Check the DNS servers configured on this host.

    TLS_INSPECTION

    502

    Your environment (customer)

    A secure connection could not be verified. The certificate presented for <host> is not trusted. This usually means a corporate proxy or firewall is inspecting HTTPS traffic.

    Params: host.

    1. Install your organisation’s root certificate on this host, or exclude the MOLO17 hosts from HTTPS inspection.

    2. Ask your network team to allow outbound HTTPS (port 443) to the hosts listed in the connectivity details.

    MOLO17_HOSTS_BLOCKED

    502

    Your environment (customer)

    MOLO17 services are blocked from this host. The internet is reachable but <hosts> cannot be. A firewall or proxy is probably blocking them.

    Params: hosts (a list).

    1. Ask your network team to allow outbound HTTPS (port 443) to the hosts listed in the connectivity details.

    2. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    BACKOFFICE_UNREACHABLE_FROM_HOST

    502

    Your environment (customer)

    The update service cannot be reached from this host. MOLO17 reports no problem, but this host cannot reach <host>.

    Params: host.

    1. Ask your network team to allow outbound HTTPS (port 443) to the hosts listed in the connectivity details.

    2. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    REGISTRY_UNREACHABLE

    502

    Your environment (customer)

    The image registry cannot be reached. This host cannot reach the container registry <host>, so new images cannot be downloaded.

    Params: host.

    1. Allow outbound HTTPS to Docker Hub (registry-1.docker.io, auth.docker.io, production.cloudflare.docker.com).

    2. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    UNEXPECTED_RESPONSE_FROM_INTERMEDIARY

    502

    Your environment (customer)

    A proxy or firewall answered instead of MOLO17. The request was answered with HTTP <status> by a device between this host and MOLO17, not by MOLO17 itself.

    Params: status, viaProxy.

    1. Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    2. Ask your network team to allow outbound HTTPS (port 443) to the hosts listed in the connectivity details.

    OTA_SERVICE_DOWN

    503

    MOLO17 services (molo17)

    The MOLO17 update service is temporarily unavailable. The update service is not responding correctly. This is on the MOLO17 side and nothing needs to change on your system.

    Params: status, host, reason.

    1. Check the MOLO17 status page for ongoing incidents.

    2. Wait a few minutes and try again.

    BACKOFFICE_REQUEST_REJECTED

    502

    MOLO17 services (molo17)

    The update service rejected the request. The update service answered HTTP <status>. This is not a network problem.

    Params: status, host.

    Contact MOLO17 support and attach the technical details.

    UNKNOWN

    502

    Unknown (unknown)

    The problem could not be identified. The checks did not point to a single cause. Share the technical details with support.

    Contact MOLO17 support and attach the technical details.

    DISK_FULL

    507

    Your environment (customer)

    Not enough free disk space. There is not enough free disk space to write <path>, and the text adds the size needed and the space available when Conductor knows them. Nothing was changed. The failing write does not always know the sizes, so the reply may name only the path.

    Params: path, neededBytes, availableBytes. Sizes are in bytes.

    1. Free up disk space on the volume that holds the Gluesync folder (docker-compose.yml), then try again.

    2. Contact MOLO17 support and attach the technical details.

    COMPOSE_FILE_CORRUPT

    500

    This installation (local)

    docker-compose.yml is empty or corrupt. <path> is unusable (<problem>, for example "the file is empty") and no last-good backup could restore it. Conductor refused to write over it.

    Params: path, problem.

    Contact MOLO17 support and attach the technical details.

    Resolution codes

    resolutionCodes lists the steps in the order to try them. This is the English text for each code.

    Resolution code Step

    WAIT_AND_RETRY

    Wait a few minutes and try again.

    CHECK_STATUS_PAGE

    Check the MOLO17 status page for ongoing incidents.

    WAIT_FOR_CONDUCTOR_UPDATE

    Wait for the Conductor update to finish. The page recovers on its own.

    CHECK_DOCKER_DAEMON

    Make sure the Docker service is running on this host.

    CHECK_COREHUB_RUNNING

    Make sure the Core Hub service is running.

    CHECK_INTERNET_CONNECTION

    Check this host’s network connection and default gateway.

    CHECK_DNS_SETTINGS

    Check the DNS servers configured on this host.

    ALLOWLIST_MOLO17_HOSTS

    Ask your network team to allow outbound HTTPS (port 443) to the hosts listed in the connectivity details.

    CHECK_PROXY_SETTINGS

    Verify the PROXY_HTTPS / PROXY_HTTP settings of Conductor and that the proxy allows these hosts.

    CHECK_PROXY_CREDENTIALS

    Verify the proxy username and password in PROXY_HTTPS / PROXY_HTTP.

    TRUST_CORPORATE_CA

    Install your organisation’s root certificate on this host, or exclude the MOLO17 hosts from HTTPS inspection.

    CHECK_DOCKER_HUB_ACCESS

    Allow outbound HTTPS to Docker Hub (registry-1.docker.io, auth.docker.io, production.cloudflare.docker.com).

    CONTACT_SUPPORT_WITH_DETAILS

    Contact MOLO17 support and attach the technical details.

    FREE_DISK_SPACE

    Free up disk space on the volume that holds the Gluesync folder (docker-compose.yml), then try again.

    Example: DISK_FULL

    A write to docker-compose.yml failed because the disk is full. Conductor answers HTTP 507 and nothing is changed. The diagnosis object in the reply body looks like this:

    {
  "schemaVersion": 1,
  "code": "DISK_FULL",
  "owner": "customer",
  "confidence": "high",
  "params": {
    "path": "/opt/gluesync/docker-compose.yml",
    "neededBytes": 52428800,
    "availableBytes": 1048576
  },
  "resolutionCodes": ["FREE_DISK_SPACE", "CONTACT_SUPPORT_WITH_DETAILS"],
  "fallback": {
    "title": "Not enough free disk space",
    "summary": "There is not enough free disk space to write /opt/gluesync/docker-compose.yml (50.0 MiB needed, 1.0 MiB available). Nothing was changed.",
    "steps": [
      "Free up disk space on the volume that holds the Gluesync folder (docker-compose.yml), then try again.",
      "Contact MOLO17 support and attach the technical details."
    ]
  },
  "checks": [],
  "source": { "service": "gluesync-conductor" },
  "at": "2026-10-24T09:15:42.000Z"
}

    Get help

    If a step does not solve the problem, or the step is to contact support, open a ticket and include the full diagnosis object, or at least its code and params. See Create a support ticket.