Bitbucket Server Backup Client fails due to Invalid Http response
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Problem
When creating a backup of Bitbucket Server by using the Bitbucket Server Backup Client, an error occurs and the backup creation does not complete.
The following appears in the atlassian-sbc-YYYY-MM-DD-MMSS.log
INFO Initializing
DEBUG HTTP GET http://localhost:7999/mvc/maintenance, headers: [Accept:[[application/json]], User-Agent:[[Wink Client v1.1.2]]]
DEBUG HTTP GET http://localhost:7999/rest/api/latest/application-properties, headers: [Accept:[[application/json]], User-Agent:[[Wink Client v1.1.2]]]
ERROR A backup could not be created. Reason: java.lang.RuntimeException: java.io.IOException: Invalid Http response
org.apache.wink.client.ClientRuntimeException: java.lang.RuntimeException: java.io.IOException: Invalid Http response
at org.apache.wink.client.internal.ResourceImpl.invoke(ResourceImpl.java:241) ~[wink-client-1.4.jar:1.4]
at org.apache.wink.client.internal.ResourceImpl.invoke(ResourceImpl.java:189) ~[wink-client-1.4.jar:1.4]
... 19 more frames available in the log fileThe log above is generated with the debug log level enabled for the Bitbucket Server Backup Client.
Cause
An incorrect port has been specified in the backup-config.properties file for the bitbucket.baseUrl property.
In the example above port 7999 is used instead of the 7990 one.
Resolution
Update the bitbucket.baseUrl to the expected value in the backup-config.properties file.