Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Atlas CORS error
See original GitHub issueI’m using atlas 2.9, with webapi security.origin to * and security.cors.enabled to false and somehow I’m still getting CORS errors when starting ATLAS
_Originally posted by @yampeku in https://github.com/OHDSI/Atlas/issues/2070#issuecomment-848609334_
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
CORS Error - Atlas - Implementers - OHDSI Forums
Hi All,. I'm having some trouble with my Atlas install. I've worked through to the last stages but now i'm hitting a CORS...
Read more >CORS error when connecting to MongoDB Atlas using Graphql
Hello, I get a CORS error when trying to connect to the atlas graphql endpoint According to @Sumedha_Mehta1 , I would not get...
Read more >Re: Atlas Cross Origin CORS - Cloudera Community - 201075
I would like to access to Apache Atlas via a XmlHtttRequest object. It doesn't work: Access-Control-Allow-Origin is missing. Thks for your help.
Read more >how to fix cors error in mongodb atlas data api - Stack Overflow
Save this answer. Show activity on this post. At this time, the MongoDB Data API does not support browser requests as CORS is...
Read more >Cannot connect to MongoDB atlas - Netlify Support Forums
It says the error “has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Recompiled WebAPI today using the newer v2.9.0 release and the CORS errors have cleared up. Was using version 2.8.2 previously. Worth a try if anyone else is having similar problems!
Sorry for the trouble @yampeku and @dormistonsmith but glad that a newer release of the platform solved this.