Data connection in Jira Cloud throws 498 HTTP response with error "Invalid JSON document"
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When you try to create a data connection, you get an error HTTP Response: 498
1
2
3
Invalid JSON document
Connected to the page but the data returned does not appear to be a valid JSON document.
Environment
Jira Cloud
Diagnosis
The JSON object that you are using contains an invisible byte order mark character at the beginning. According to the JSON standard, JSON text should not begin with a byte order mark, and this is the reason that our JSON parser rejects the supplied value.
If you open the URL in the Mozilla(or other) browser you can see errors like:
1
SyntaxError: JSON.parse: unexpected character at line 1 column 482013 of the JSON dataTrying to validate the JSON, you can see the below errors:
1
2
3
4
Parse error on line 1:
...", "echeStartDate": NaN, "echeEndDate":
-----------------------^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'Cause
The additional space or invalid character at the beginning of the JSON text.
We did have known bugs with certificate issues by Sectigo but this has been fixed now.
Solution
Review the JSON data to remove the invalid character. A simple workaround would be to prepare a JSON object that does not begin with this character.
Verify that the certificates are valid
If you still encounter an issue please contact Atlassian Support
Was this helpful?