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

Cross-origin HTTPS request (CORS) causing Trello to be unusable in Chrome?

Deleted user May 30, 2017

Is anyone else experiencing this issue while using Chrome Version 58.0.3029.110 (64-bit) and accessing Trello? I can log in fine, but my boards won't display unless I disable CORS checking with a plugin. Restricting cross-origin HTTP and HTTPS requests seems like a common thing in modern browsers, so would the fix be as simlpe as adding the Access-Contorl-Allow-Origin header to Trello? This could be causing lots of Trello users pain.

From Chrome developer tools:

Access to Script at '' from origin '' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin '' is therefore not allowed access.

1 answer

2 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 31, 2017

For performance reasons, Trello loads resources from its content delivery network (CDN), which is located at, and it looks like Chrome is rejecting those resources because they're coming from a domain other than

There's a way to use resources from other domains that tells the browser, "Hey, don't worry, it's ok to load these resources even though the domains don't match," which is why our users don't typically see this error. However, some proxies or firewalls strip these CORS headers that give the browser the OK, and I think that's what's happening here. Not every browser blocks resources from external domains, but Chrome does.

If that doesn’t load, there are a few common potential causes, such as DNS cache issues or a firewall blocking access. For more information about how to troubleshoot those issues, please see:

Hey Torben.

Thanks for the quick reply. I'm still having to use the plugin that disables CORS, much like starting Chrome with the --disable-web-security flag. Otherwise I get four scripts blocked by the CORS policy as seen in Chrome's developer tools: snowplow, quickload, ltp, and locale.en-US.

Internet Explorer 11 and Edge both work fine, both at work and at home. I can load the Trello test CDN pages in Chrome. This is also across two devices, one Windows 7 the other Windows 10. The Windows 10 device is a clean install of the OS in the hopes a fresh start would fix Chrome.

At this point I'm stumped.

I'm getting the same issue in Firefox Developer 102.0b7 (64-bit). There's no CORS header, and Trello is fully unusable.

trello cors.png

Like byte916 likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events