bmcalary Atlassian Team

@Geordie McCabe I looked into your error and IP. It appears your IP was making over 1 million requests to /rest/api/2/search within a 10 minute period at 22:00 UTC Aug 27 and again 00:20 UTC Aug 28. This is 1600+ requests per second to the same endpoint. As a result, your client/IP was temporarily blocked by our automated…

@Zhishang Zheng AWS logged it as a successful response with a 200 OK response code. The only thing somewhat interesting is that AWS logged the following: * time-to-first-byte: 1.923s (this is how long it took from the receipt of the request till Atlassian sent the response to Cloudfront) * time-taken: 6.923s (this is how…

@Zhishang Zheng That issue was created by Atlassian ID 5a837474f3564698bccedeecc0066d45 Cloudfront ID kpiZ6SrP7tvqUDPWFPkhEEfSV_OKXqTEs6xZsomwG_EO4JpZDXHgXw== 

@Zhishang Zheng what is your axios `timeout` currently set to? The log you shared shows your client was in "read" state which is awaiting a response from Jira, but gave up on your side due to encountering a timeout. Try adding the following to your axios client config. <span>timeout</span>: <span>60000</span>,…

@Kanak Kabara Thanks for mentioning the library you are using, that was very helpful. Atlassian does not maintain that library directly, but I have gone ahead and raised a Github Issue with the maintainers for you here https://github.com/pycontribs/jira/issues/1945 . It would be good if you could share any minimal code…

@tomislav.smrecki it appears that https://github.com/UpHabit/semantic-release-jira-releases/blob/master/lib/success.ts depends on https://www.npmjs.com/package/jira-connector?activeTab=readme and I believe the problem is here on line…

@Samuel Cebrian I will respond on the github issue, as this appears to be related to a 3rd partry library/integration. https://github.com/Icinga/icingaweb2-module-jira/issues/143 

Nice find. Great work.

@Zhishang Zheng hello again! This is due to https://community.atlassian.com/t5/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153 , which is due to new DDOS protection by Cloudfront. As the article says, rollout is progressive, so some requests will work, some might fail…

@Zhishang Zheng our logs indicate your client is sending a GET with a BODY payload. Please refer to this guide https://community.atlassian.com/t5/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153 

@Zhishang Zheng Upon inspection of our AWS Cloudfront logs, your request was rejected because it contained a GET with BODY. Please refer to this guide on how to fix it https://community.atlassian.com/t5/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153 

@Mary Glo De La Pedra we are seeing two bytes of body in both cases. It works from your laptop because we have not completed our rollout to your origin Country yet. However your API request is coming from a country where our rollout has been completed. If you are using libcurl inside PHP please make sure for GET requests…

@Mary Glo De La Pedra it appears your integration with our API is sending a malformed GET with a BODY, please refer to this guide on how to resolve the issue https://community.atlassian.com/t5/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153 If you need further…

@Tech Habiteo Our records indicate this failure was not due to a WAF denial, but could be due to including a body in a GET request. Can you please ensure your HTTP client is not setting any request body when performing a GET.

@Timothée Ville Ben from Atlassian Networking. I checked and it looks like this was an invalid request. Is it possible you accidentally included a body/data with a request of type GET? GET type requests do not allow request body data. If this is not the issue, please open a support case at support.atlassian.com

@Claudia Alvarez I checked our logs and can't find this event. Is this still occurring? If so, can you share the domain you are visiting with me (i.e the one that appears in your browser's URL bar?)

@Hemanth Kumar L G xray.cloud.getxray.app is a 3rd party domain not owned or operated by Atlassian. They appear to develop tooling and addons on top of Atlassian products. I suggest getting in contact with them via their support desk here:…

@Hemanth Kumar L G what was the domain name in the browser address bar when this message appeared?

@Silas Belau Sorry to hear that. What domain appeared in your URL bar when this happened?

@GANGA DHARARAO Ben from Atlassian Network Engineering, can you please share the Request ID printed on the screen, and the domain name that appears in the URL bar of your browser?

@Juan Camilo Rodriguez Rios do you require further assistance? We're happy to work through the original issue with you if you can replicate it.

@Juan Camilo Rodriguez Rios this may have been transient. Are you still seeing the error? If so please provide a fresh request ID and the domain that is appearing in the URL bar. Thanks.

UPDATE 25/1/25: Jira Cloud now uses AWS Cloudfront. AWS Cloudfront blocks GET requests with a Body payload. See https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html#RequestCustom-get-body Most commonly we see API clients and integrations sending {} [] "" '' . Please…

@Mamadou NDIAYE I will respond over in https://community.atlassian.com/t5/Jira-Software-questions/The-request-could-not-be-satisfied-custom-jira/qaq-p/2512143

@Madenietov Alisher @Abdenova Asel we're made some changes. Can you access the product now?

Thanks @Madenietov Alisher we're looking into this now. I'll keep you updated.

@Abdenova Asel what URL was in your browser address bar at the time of this message?

@K Rahul you should see a CAPTCHA now instead of being completely blocked. Let me know if you can get through. Apologies for the inconvenience.

@Isadora Antunes Lourenço Pereira the cause of those failure is the same as the one here https://community.atlassian.com/t5/Jira-questions/Re-Getting-403-error-the-request-could-not-be-satisfied/qaq-p/2438896/comment-id/587159#M587159 Your source IP has been flagged as a source of malicious activity. We have added an…

@Pookie your issue is slightly different to the one in https://community.atlassian.com/t5/Jira-questions/403-ERROR-The-request-could-not-be-satisfied-Request-blocked-We/qaq-p/2431112 Your source IP address, which I won't share here but which you can see by visiting http://checkip.amazonaws.com/ , was flagged as being…