I’m guessing that some authorization mechanism of yours is blocking access to that endpoint.
The version number is mentioned in the ticket I linked to in my previous reply to you:
latest onpremise Sentry in docker: Sentry 20.12.0.dev055c4673
@mbonaci Thanks for replying.
1 Like
If the integration fails with a GET <Jira Cloud instance>/atlassian-connect/all.js net::ERR_ABORTED 404 error message, that’s because Jira Cloud changed the way the all.js is used as described in details in the Deprecation of xdm_e Usage - Announcements - The Atlassian Developer Community post.
Sentry has been updated to use the new path as part of fix(jira): update all.js path for Jira by scefali · Pull Request #18489 · getsentry/sentry · GitHub but the error can still occur when using an older version of on-premise Sentry.
If I’m reading the changelog right, the fix is available starting from version 20.6.0.
I’m not sure if there is a workaround for earlier versions, but I’m posting it here to see if this community can help.
1 Like