---
title: "CMJ - Connection failed error during snapshot deployment"
canonical: "https://support.appfire.com/space/SUPPORT/668729553/CMJ%20-%20Connection%20failed%20error%20during%20snapshot%20deployment"
format: markdown
---
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](media://feeb7c2d-826b-45cf-97e8-a82d1666dac9)


### :root-cause: Root Cause

HAR file analysis revealed multiple HTTP error responses:

- `401 Unauthorized`
- `0` (request not completed)

![image-20260325-041605.png](media://7c723b2f-20ae-4518-ac92-4807bb899133)

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. 

- Navigate to **Jira Admin > System > General Configuration**
- Verify that the **Base URL** matches the accessible domain (e.g., `jira3.ext.net.example.com`)
- More details as in [https://confluence.atlassian.com/adminjiraserver/configuring-the-base-url-938847830.html](https://confluence.atlassian.com/adminjiraserver/configuring-the-base-url-938847830.html) .