Timeout or proxy error when deploying snapshot
Symptoms:
Deploying a snapshot results in one of the following errors:
Unknown: This site is currently undergoing maintenance. We apologize for the inconvenience. Proxy error.
Unknown: 504 Gateway Timeout
Request terminated: The current operation was terminated unexpectedly.
Often these errors come with no visible error in the Jira logs reported.
Cause:
These kind of errors usually indicate a client side or a network issue, i.e. something is terminating the request before it reaches the server. Firewall, proxy and browser timeouts are a common reason for such errors.
Note: there are several possible places where CMJ can hit network timeouts. Such errors are not expected during the heavier operations such as creating/deploying a snapshot or calculating the Diff, where CMJ uses frequent polling. Uploading the snapshot file uses a long-running HTTP call and could time out depending on network settings and file size.
Timeouts on long-running user requests are almost always caused by an inbound reverse proxy or load balancer sitting in front of Jira. There is no setting in CMJ for this. If you are using a reverse proxy or load balancer, please check their respective timeout settings. You can also try bypassing the proxy to verify if the timeout error still occurs.
If the system is not behind a proxy, please check the Tomcat settings.
Also, you could check how long exactly the current timeout is in the browser dev tools when the CMJ request times out.
Summary:
From Jira’s UI you can inspect outbound proxy flags and run health checks, but the fix is almost always at the reverse proxy / load balancer: raise timeouts (often to ≥300s), enable sticky sessions, and confirm by bypassing the proxy.
Resolution:
Option 1 - use the 'Path to snapshot file' feature:
You can either upload a snapshot file or select a path to a snapshot on current Jira's file system. This way, you can copy large snapshots directly to a location on the target Jira's file system, so you don't need to upload them from the browser. These are two alternative approaches to load a snapshot file.
Option 2:
The following actions could aid in the problem resolution:
If there is a proxy/firewall between the client machine and the destination server, increasing the timeout will keep longer running operations from terminating
Generating and analyzing a .HAR file of the network traffic from the time of the error helps identify request timeouts
Working together with a network administrator can help analyze the network infrastructure
Atlassian guide for troubleshooting network and connectivity issues:
See: