Server Unreachable - Timeout when merging or viewing Diff of pull request

Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Upon merging a pull request the merge dialog will be displayed for around 30 seconds before timing out with "Server Unreachable – The server didn't respond. You may retry your request when the server comes back up." Note that refreshing the page in the browser actually shows that the pull request was merged. The "Delete Branch" option doesn't work and the timeout message is also seen when viewing the diff of a pull request. Also, pushing code via command-line gets to the point where all objects are written 100% and then pauses for ~45 seconds before finally completing.

Message seen on the screen:

(Auto-migrated image: description temporarily unavailable)

Cause

Browser-side code will timeout after one minute. The merge completes because the HTTP POST leaves the customer browser after clicking "Merge". It arrives at the Bitbucket Server instance which processes it but the response to the POST is lost on the way back to the client. Possible causes:

Diagnosis

  • Bypass the reverse proxy to try and fix the problem.

    (Auto-migrated image: description temporarily unavailable)

  • Check you network latency.

  • Check your browser:

    • Test access with different browsers/versions

    • Run your browser in "safe mode" to isolate it from installed plugins that could be causing the issue (i.e.how to start firefox in "safe mode")

    • Check your browser configuration for a proxy that could be causing the issue. Bypass this proxy.

  • Check your logs for Bitbucket Server Plugin Issues

    • Awesome Graphs: check for messages like the ones below:

      2014-05-09 00:08:10,479 DEBUG [pool-8-thread-1] com.atlassian.bitbucket.scm.BaseCommand Executed /usr/local/bin/git log 3472f5f866c30e31758853016401189e3b02b6d2 --pretty=format:%H --shortstat --no-merges 2014-05-09 00:08:10,479 WARN [pool-8-thread-1] c.s.s.g.s.LogThrowableExitHandler Unable to execute command completely: /usr/local/bin/git log 3472f5f866c30e31758853016401189e3b02b6d2 --pretty=format:%H --shortstat --no-merges. Throwable: com.atlassian.utils.process.ProcessTimeoutException: process timed out 2014-05-09 00:08:10,479 WARN [pool-8-thread-1] c.s.s.g.idx.GraphsIndexingService ((Diffs)) -> 359 2014-05-09 00:08:10,551 WARN [pool-8-thread-1] c.s.s.graphs.idx.GraphsIndexingJob GraphsIndexingJob --> stop() 2014-05-09 00:08:10,551 WARN [pool-8-thread-1] c.s.s.graphs.idx.GraphsIndexingJob GraphsIndexingJob --> start() 2014-05-09 00:08:26,898 DEBUG [pool-8-thread-1] com.atlassian.bitbucket.scm.BaseCommand Executed /usr/local/bin/git rev-list --format=%H%x02%h%x02%P%x02%p%x02%aN%x02%aE%x02%at%n%B%n%x03 --stdin -- 2014-05-09 00:08:26,900 WARN [pool-8-thread-1] c.s.s.g.idx.GraphsIndexingService (()) -> 8592

    • ScriptRunner: check for ScriptRunner-related errors, for example:

      2026-08-13 14:58:38,305 ERROR [https-jsse-nio-8443-exec-28] user *1Q39HNAx897x33471639x0 y2v7p2 ... "GET /rest/ui/latest/projects/PROJ_KEY/repos/repo_slug/pull-requests/1596/merge HTTP/1.0" c.a.p.r.v.e.ThrowableExceptionMapper Uncaught exception 99bb0f94-8817-4473-acfb-2dcace540f71 thrown by REST service: org/apache/log4j/spi/LoggingEvent java.lang.NoClassDefFoundError: org/apache/log4j/spi/LoggingEvent ... at com.atlassian.bitbucket.internal.rest.pull.InternalPullRequestResource.canMerge(InternalPullRequestResource.java:57) ... at com.atlassian.stash.internal.hook.repository.DefaultRepositoryHookService.preUpdate(DefaultRepositoryHookService.java:844) at com.atlassian.stash.internal.pull.DefaultMergeRequestCheckService.checkMergeability(DefaultMergeRequestCheckService.java:48) at com.atlassian.stash.internal.pull.DefaultPullRequestService.canMerge(DefaultPullRequestService.java:292) ... Caused by: java.lang.ClassNotFoundException: org.apache.log4j.spi.LoggingEvent not found by com.onresolve.stash.groovy.groovyrunner [122] at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1591)

  • To see if the problem is being caused by "Git 1.8.3.XandGit 2.2.x - 2.4.0" or BSERV-7360 - Front end for pull request merges should wait as long as server does for process to completeor BSERV-7457 - Cross-repository pull request merges sometimes fail to fetch objects after upgrading to Stash 3.9

    • Enable your Bitbucket Server Profiling logging

      • Look for the following profiling event:

        2015-06-01 11:37:47,273 | drift:thread-1 | - | - | - [121430ms] - Drift: Calculate for com.atlassian.bitbucket.internal.pull.comment.drift.DriftCommentUpdateProcessor$CommentDriftCalculator@76cec2d0 [121368ms] - Drift: Map anchors 3193 [16ms] - Set com.atlassian.bitbucket.internal.pull.comment.CommentPostProcessor.processAll(InternalCommentable,Set) [16ms] - com.atlassian.bitbucket.internal.comment.PluginCommentPostProcessor.processAll 1 comments [16ms] - com.atlassian.bitbucket.internal.comment.like.property.CommentLikePropertyProvider.provideProperties for 1 comments [121336ms] - git: with pull request lock 2:2533 [15ms] - InternalPullRequest com.atlassian.bitbucket.internal.pull.PullRequestDao.findByRepositoryScopedId(int,long) [121321ms] - git: resolve effective diff 2533@1 [120744ms] - git: create new merge 2533@1 [120681ms] - git: merge <USERNAME>/<REPOSITORY>:refs/heads/client_seeding_cleanup -> <PROJECT>/<REPOSITORY>:refs/heads/development [172ms] - git: clone 2 [172ms] - C:\Program Files (x86)\Git\cmd\git.exe clone --no-checkout --shared -b development D:\Atlassian\bitbucket-home\shared\data\repositories\2 D:\Atlassian\bitbucket-home\tmp\git\<REPOSITORY>-work7276869962633828049.git [140ms] - git: reset 818beae5e0bb5faa3998e7fe5bce3b64f2318185 [140ms] - C:\Program Files (x86)\Git\cmd\git.exe reset --quiet 818beae5e0bb5faa3998e7fe5bce3b64f2318185 -- [328ms] - git: merge 57fab50d40b6286ae12f20d8cfb4d96c3f47945b [328ms] - C:\Program Files (x86)\Git\cmd\git.exe merge -m Automatic merge --no-ff --log 57fab50d40b6286ae12f20d8cfb4d96c3f47945b [120041ms] - git: fetch 2 [120041ms] - C:\Program Files (x86)\Git\cmd\git.exe pack-objects --delta-base-offset -q --stdout [514ms] - git: resolve merge-base 2533@1 [483ms] - git: fetch client_seeding_cleanup for 2533@1 [483ms] - C:\Program Files (x86)\Git\cmd\git.exe fetch D:\Atlassian\bitbucket-home\shared\data\repositories\183 refs/heads/client_seeding_cleanup: [31ms] - C:\Program Files (x86)\Git\cmd\git.exe merge-base 57fab50d40b6286ae12f20d8cfb4d96c3f47945b 818beae5e0bb5faa3998e7fe5bce3b64f2318185 [47ms] - git: update refs 2533@1 [32ms] - C:\Program Files (x86)\Git\cmd\git.exe update-ref bitbucket-refs/pull-requests/2533/from 57fab50d40b6286ae12f20d8cfb4d96c3f47945b 3ea38ec83a47bb90eaca5774e062c561e296ffd3 [15ms] - C:\Program Files (x86)\Git\cmd\git.exe update-ref bitbucket-refs/pull-requests/2533/merge 818beae5e0bb5faa3998e7fe5bce3b64f2318185 [62ms] - Drift: Strategy - Composite (FileComment, FastForward, Diff, OrphanAll) 3193 [31ms] - Drift: Strategy - FastForward 3193 [31ms] - Drift: FastForward - Merge changes [3ea38ec83a47bb90eaca5774e062c561e296ffd3]->[57fab50d40b6286ae12f20d8cfb4d96c3f47945b] 3193 [31ms] - C:\Program Files (x86)\Git\cmd\git.exe diff-tree -C -r --format=%H 3ea38ec83a47bb90eaca5774e062c561e296ffd3 57fab50d40b6286ae12f20d8cfb4d96c3f47945b -- [31ms] - Drift: Strategy - Diff 3193 [31ms] - Drift: Diff - Merge diff [3ea38ec83a47bb90eaca5774e062c561e296ffd3]->[57fab50d40b6286ae12f20d8cfb4d96c3f47945b] 3193 [31ms] - C:\Program Files (x86)\Git\cmd\git.exe diff -C --color=never -U0 --dst-prefix=dst:// --src-prefix=src:// 3ea38ec83a47bb90eaca5774e062c561e296ffd3 57fab50d40b6286ae12f20d8cfb4d96c3f47945b --

    • Git 1.8.3.X

      • If the operation is taking a long time on the [172ms] - git: clone line, that's likely Git 1.8.3

    • BSERV-7360 - Front end for pull request merges should wait as long as server does for process to complete

      If the operation is taking a long time on the [328ms] - git: merge line, that's BSERV-7360

Resolution

For each of the causes above, the solution would be:

Updated on August 18, 2026
Platform
Data Center only
App
Bitbucket Data Center
On this pageSymptomsCauseDiagnosisResolution

Still need help?

The Atlassian Community is here for you.
Ask the Community