'ERROR A backup could not be created. Reason: Lexing failed on line: 1..' When creating a backup using the backup client

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When creating a backup using the backup client, the following error appears in the terminal:

2014-02-05 15:56:28,920 INFO Initializing
2014-02-05 15:56:30,760 INFO Contacting Bitbucket Server
2014-02-05 15:56:31,057 ERROR A backup could not be created. Reason: Lexing failed on line: 1, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
groovy.json.JsonException: Lexing failed on line: 1, column: 1, while reading '<', no possible valid JSON value or punctuation could be recognized.
at groovy.json.JsonLexer.nextToken(JsonLexer.java:82) ~[groovy-all-2.1.6.jar:2.1.6]
at groovy.json.JsonSlurper.parse(JsonSlurper.java:73) ~[groovy-all-2.1.6.jar:2.1.6]
... 9 more frames available in the log file

Cause

This happens if Bitbucket Server can't validate the JSON file from Bitbucket Server due to the following reasons:

  • If there is an Apache setup that redirects to a different port.
  • If you are using SSL in Bitbucket Server and the bitbucket.baseUrl set in the backup configurations is a non-SSL URL redirects to the SSL URL.

 

Workaround

Set the bitbucket.baseUrl in the backup configurations to the original servername with the original port. For example: servername:7990 instead of servername:80

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.