Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-6989

Backup Client Fails When Specifying Incorrect Protocol for Base URL

      If you perform a backup with the backup client, and you specify http:// for the base URL rather than https:// (if Stash is configured to expect HTTPS), then the backup will fail with the following error:

      dlahn@fecru35pg:/opt/atlassian/stash-backup-client-1.6.0$ sudo java -jar stash-backup-client.jar
      2015-01-14 14:00:40,324 INFO         Initializing
      2015-01-14 14:00:43,611 ERROR        A backup could not be created. Reason: Unable to determine the current character, it is not a string, number, array, or object
      
      The current character read is '<' with an int value of 60
      Unable to determine the current character, it is not a string, number, array, or object
      line number 1
      index number 0
      <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      ^
      
      groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or object
      
      The current character read is '<' with an int value of 60
      Unable to determine the current character, it is not a string, number, array, or object
      line number 1
      index number 0
      <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
      ^
      	at groovy.json.internal.JsonParserCharArray.decodeValueInternal(JsonParserCharArray.java:216) ~[groovy-all-2.3.6.jar:2.3.6]
      	at groovy.json.internal.JsonParserCharArray.decodeValue(JsonParserCharArray.java:166) ~[groovy-all-2.3.6.jar:2.3.6]
      	... 13 more frames available in the log file
      

      This error message should be amended by provide more details about where the problem is coming from. (i.e. the base URL doesn't match.)

            [BSERV-6989] Backup Client Fails When Specifying Incorrect Protocol for Base URL

            No work has yet been logged on this issue.

              pepoirot Pierre-Etienne Poirot (Inactive)
              dlahn David Lahn (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: