nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Vishwanath RK

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

JIRA Set Up Page.PNG

JIRA Set Up Error.PNG

Accepted answers

bmcalary

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.

All comments

Uma Talpakova

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

Jason Schaufele

I'm having this issue too.

Agustin Alarcon

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

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

jguitartp

Same problem when log in on sourcetree

Michael Evangelista_7sweas

Same here.

bmcalary

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

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.

Abdenova Asel

i have too... in all office

Request ID: m-bbAbz-yQ8Q9OFoDAXghoGCnjeA07rNfrNPMEPK_5jSj37B5chbDA==

Abdenova Asel

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.

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.

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?

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.

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.

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.

sofia_crona

Hi!

Since yesterday I suffer from the same issue: Both for access to Jira and Confluence.
Here are some of my Request Id:

Request ID: MBFkQ16kG85HGDwH0CbQMQhEj0p6VP1crWDZk_DfQSYVzw6tmcHACw==

Request ID: WL5KRd8jwf7y1EImI8xYbSgYmYC659mgg4_uU52rdFTfJ83zSWQPow==

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

bitbucket

atl-rvw