403 ERROR The request could not be satisfied. Request blocked. We can't connect to the server for th

[Vishwanath RK]

Hi

After installing JIRA and during set up, click on continue to MyAtlassian giving an error.

[bmcalary · Accepted solution]

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 ensure your API client does not include a body with a GET request. This information only applies to API clients and integrations, not browsers.

Hello,

Ben from the Atlassian Networking Team.

We believe this was caused by a over-zealous web application firewall rule.

We believe we have fixed the problem. Can you please retry and let us know?

If it's still not working, can you please give us the "Request ID" printed at the bottom of the screen?

Ben.

[swara.s]

I am facing the same issue.
This is the request id: 

fbuUABXEduTvLP1DvVpnzjdbKd-JxrsosE2ZsmirUBM1MAEJMzrUTA==

Error: Request blocked. 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.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

[bmcalary]

@swara.s Please try again. :)

[swara.s]

Yes, now its working.
Thanks sir :)

[Jason Schaufele]

Thank you. Its working now.

[Mary Glo De La Pedra]

Hi @bmcalary , our team is facing the same issue. It was working fine then suddenly encountered the same issue.
Request ID: fHQfGqZoWX8r74xaTAAhHgp8HAgqGbFLlq56qhcCedEn8giF_A5xPQ==

In addition, we don't have Body to our 'GET' requests but it is still returning an error.

Thanks.

[bmcalary]

@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 assistance please reach out to us and reference this conversation 

https://support.atlassian.com/contact/ 

[Mary Glo De La Pedra]

Hi @bmcalary , hmm. that's weird because, in my local, it works fine but not in our testing and production environment. Also, I'm using cURL (PHP) and there's no body field passed using  'GET' cURL request. Do you have a log of the API request sent to your end?

Thanks.

[Zhishang Zheng]

Hi @Mary Glo De La Pedra , our team faced a similar issue recently, when we make http requests via rest API V3, we randomly got "HTTP/1.1 403 Forbidden", with error "ERROR: The request could not be satisfied".

Could you kindly help take a look? Take this request for example, it's just a simple get:
Request ID: JVH0GMkVp3T4_oUeQzB3wzZAWmQPadKXhXbUg5jqKppRUT621QTXpQ==

[bmcalary]

@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]

@bmcalary , thanks for the info.

Indeed we pass in an empty string as body in case of a GET request in js.

We've update our code and fixed the issue with your help in the other jira ticket:

https://community.atlassian.com/t5/Jira-questions/The-request-could-not-be-satisfied-custom-jira/qaq-p/2512143

Again, thanks for your help!

[Agustin Alarcon]

Same problem since yesterday, I cannot log in on Sourcetree because of this.

[Jason Schaufele]

I'm having this issue too. 

[Uma Talpakova]

I have the same issue, I cant handle it since yesterday. 

[tomislav_smrecki]

Hi, same issue here since a couple of days ago.
Here's the latest retry, Request ID:
sd78v78ALs0O-nuOtFrx2hhSRP4WlAcW2aqW2WTLxbc1Il86B6uR0g==

I'm using third-party semantic-release-jira-releases plugin which is quite old so it might need some update.

[bmcalary]

@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 302 https://github.com/floralvikings/jira-connector/blob/45d661db84de13997a7712c8629d2da31875297c/api/project.js#L302 

if (!body) body = {};

From our logs we see semantic-release-jira-releases including 2 bytes of text in the body, so this should be it.

Unfortunately, the author of the dependency no longer maintains the project, and recommends https://github.com/MrRefactoring/jira.js instead.

You could possibly patch the original library directly in your project folder, or you could raise an issue with the maintainers of https://github.com/UpHabit/semantic-release-jira-releases/tree/master to ask them to switch over to https://github.com/MrRefactoring/jira.js

Ultimately this issue is the result of our DDOS protection rollout mentioned here https://community.atlassian.com/t5/Atlassian-Platform-articles/Jira-Confluence-Cloud-APIs-return-403-Error-The-request-could/ba-p/2928153 

[tomislav_smrecki]

Great, thank you for confirming the issue!

There are already some forked versions of the plugin so if anyone comes across a similar issue, it might be worth looking into those options.

[Tech Habiteo]

Hello, I have the same problem, could you check it please ?

Request ID: 5onJUG83MSNpPiblQ6OWuJUPDkhnpq6JyPxUkbsbidBKvlDxnf0Qdg==

[bmcalary]

@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]

Hi everyone!

I'm also having this issue while trying to call the reporting API endpoint of Atlassian Marketplace.

Request ID:

QwJd_h4HDKHfxNHB621_PSfiTZClw7iipXp0Jjp3_eYgMGAnJXr51g==

[bmcalary]

@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

[Timothée Ville]

Ok, my bad! Didn't see I had a body.
It's working fine.

Thank you @bmcalary and sorry for the false alert.

[Silas Belau]

@bmcalary I am also facing the same issue

Request ID: 2tQVSyRbpE26oRlcl8BLL9uQtnxXJNr_HmxX9DSYQUuMp4RXBviu9Q==

[bmcalary]

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

[Juan Camilo Rodriguez Rios]

Hi, same here. Mi Request ID: BlSc7kIalTgg46UxUZOMEDhT1e2i0bWT3EOWHBR3N8DJai6amrhD2Q==

[bmcalary]

@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.

[Juan Camilo Rodriguez Rios]

Thanks @bmcalary . I had to stop using n8n.io trello node and configure my own custom webhooks.

[bmcalary]

@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.

[Hemanth Kumar L G]

@bmcalary  We are also facing the similar issue
"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"

Request ID: BZWiJ2u6E1syLCSjQL0fqvzWzrnzAXBpc4HG7DZkydwusEQQSYJy1g==

[bmcalary]

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

[Hemanth Kumar L G]

lilly-jira.atlassian.net this is our domain name.

https://xray.cloud.getxray.app/api/v2/graphql this is the endpoint we were hitting

[bmcalary]

@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:

https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2

[Claudia Alvarez]

Hi, I'm having this issue too: 

<H1>403 ERROR</H1>

<H2>The request could not be satisfied.</H2>

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.

If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Request ID: PtjkIrPsaKqSiruuRNeMH7ludx384pr7aa04Wa26pFm2k4He-1_U6Q==

[bmcalary]

@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?)

[Abdenova Asel]

i have too... in all office 

Request ID: m-bbAbz-yQ8Q9OFoDAXghoGCnjeA07rNfrNPMEPK_5jSj37B5chbDA==

[bmcalary]

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

[Madenietov Alisher]

hello, she is working with me in office, url this 
https://trello.com/b/8BMX8RY2/сервис-гактау 
and in sometimes we have 403 error 
The request cloud not be satisfied, this problems started 5 days ago and have now

[bmcalary]

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

[bmcalary]

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

[Isadora Antunes Lourenço Pereira]

Hi,

I'm having the same problem today

[bmcalary]

@Isadora Antunes Lourenço Pereira can you please provide me with the Trace ID printed at the bottom of the error message, or a screenshot?

[Isadora Antunes Lourenço Pereira]

Sure!

ACK6h8Bmciz67-ruTt6VRunHH7KohO5uYCSVCkKr5dEEifh49XefVg==

[bmcalary]

@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 override. This should resolve the problem.

We strongly recommend following the instructions in that linked comment to inspect the reasoning for the poor IP reputation.

[Isadora Antunes Lourenço Pereira]

Oh, thank you very much sir

[K Rahul]

@bmcalary I am also facing the same issue

Request ID: tLEb7f3MqcErhJHkX_m_18Q1OnAwkN8obQgPE9k-wClg4beee6wcYQ==

[bmcalary]

@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.

[Michael Evangelista]

Same here. 

[jguitartp]

Same problem when log in on sourcetree

[Ste Wright]

Hi All,

I can let Atlassian know, but I'd also encourage you to report your issues via https://support.atlassian.com/

Ste

[Abdenova Asel]

Request ID: m-bbAbz-yQ8Q9OFoDAXghoGCnjeA07rNfrNPMEPK_5jSj37B5chbDA==