/
CMJ - Connection failed error during snapshot deployment

CMJ - Connection failed error during snapshot deployment

This article addresses a connection failure issue encountered when deploying a snapshot using Configuration Manager for Jira (CMJ).

 

Jira Environment

Data Center

Problem

While deploying the snapshot, CMJ loses connection to the Jira server. This is typically accompanied by the following message:

Connection failed

Configuration Manager for Jira has lost connection to the server.

This error might be caused by a network problem on the client machine or a request termination due to timeout.

If the problem persists, try the following:

  • Increase the timeout for any proxy or firewall between the client machine and the Jira server.

  • To rule out browser-related problems or timeout, try a different browser.

  • To identify request timeouts, generate and analyze a .HAR file of the network traffic from the time of the error.

  • To avoid delays for large snapshots, copy the snapshot on the target system and provide its location on: Deploy > From Snapshot File > Path to snapshot file.

  • Analyze the network infrastructure with the help of your network administrator.

Try creating a new diff to see if the problem is resolved.

image-20251226-201848.png

 

Root Cause

HAR file analysis revealed multiple HTTP error responses:

  • 401 Unauthorized

  • 0 (request not completed)

image-20260325-041605.png

The issue results from a mismatch between the Jira base URL configuration and the actual deployment URL. CMJ uses the base URL to generate deployment operation paths. If the base URL is incorrectly configured (e.g., pointing to .int while the UI access is via .ext), CMJ polls the wrong endpoint, leading to authentication failures.

  • Snapshot deployment initiated at:
    https://jira3.ext.net.example.com/rest/configuration-manager/1.0/deployment

  • CMJ returned deployment polling path:
    https://jira3.int.net.example.com/rest/configuration-manager/1.0/deployment/6

Note that this points to jira3.int and not jira3.ext.

The difference in domains (.ext vs .int) caused polling to fail with 401 status.

Solution

This is a problem with the configuration of Jira’s base URL. It is recommended to check and Correct Jira Base URL.