Dear Atlassian Community,
I am frequently encountering a 403 ERROR when making API calls to Jira for creating issues. The error message suggests that the request is being blocked by CloudFront, and I am unable to determine the exact cause.
Issue Details:
- API Endpoint: https://wotnot.atlassion.net/rest/api/2/issue
- Authentication Method: Basic Auth (email + API token)
- Request Headers:
{
"Accept": "application/json",
"Content-Type": "application/json",
"X-ExperimentalApi": "opt-in", "X-Atlassian-Token": "no-check"
}
- Error Message (Full Response):
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>403 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
Bad request.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: ojUc0h5IjJKN0XMTBuyYnDzKbtiwU-tc7Xk961rZFVi0NGSZ7K1m8g==
</PRE>
</BODY></HTML>
Troubleshooting Steps Taken:
✔ Verified API token and authentication using /myself API (works fine).
✔ Confirmed that my user has Create Issue and Browse Project permissions.
✔ Checked CloudFront request logs but found no specific reasons for blocking.
✔ Disabled VPN and tried different networks, but the issue persists.
✔ Implemented retry logic in case of temporary blocking, but no success.
Request for Assistance:
- Is there any known issue with Jira API calls being blocked by CloudFront?
- Are there specific rate-limiting rules or security policies that might be causing this?
- Would adding specific request headers (e.g.,
User-Agent) help bypass this issue? - Any suggestions on how to resolve or further debug this?
Any guidance or suggestions would be greatly appreciated!
Best regards,
Avi Paghadar
avi.paghadar@wotnot.io
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.