Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

CORS Issue in Marketplace after Upgrading to Confluence Data Center 7.4.14


After upgrading my Confluence Data Center instance to 7.4.14, I am getting CORS errors on the "Manage apps" screen when expanding some of the plugins on my instance.  You can see the issue here:

As you can see, it looks like a request is getting blocked from the following URL:

I have already tried adding a whitelist for the domain, which you can see here:


I have also added the following the following modification to the web.xml file (as suggested here):

<!-- MBZ: Added CORS Headers -->


1 answer

@William Yeack Try unchecking the setting "Connect to the Atlassian Marketplace" on the Manage Apps page. 


Screen Shot 2021-12-17 at 1.58.09 PM.png

Hi @Sundar Radhakrishnan - so I went back to check and the problem seems to have been resolved.  I am guessing that the Atlassian wasn't giving the right headers on their side and then they fixed things?

@William Yeack Looks like that. When I was facing the same issue this morning EST, saw errors on the browsers' console related to CORS when our local Jira app was calling marketplace API to fetch the plugin's info.So, they could have added XSS related headers in the response and set it to block. Or they would've enabled CORS at their backend (API or at the firewall side) and removed it.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events