It isn't a CORS issue. You're getting a 500 error on the back-end which responses without the proper CORS header.
Check your logs to see what causes the 500 error.
For me, it works if I just remove includeTracks.
Summer Sale! All accounts are 50% off this week.
Hi,
I've been developing a API filter/ include relationship logic locally. It's here: https://app.moos.nu/api/v1/installations/?filter[client]=001&includeSensors&includeTracks
This works locally. But not remotely. My API client throws a 500 error, without body returned for the response. In my browser it says "CORS missing allow origin". If I remove the includeSensors and includeTracks bit it does work (feel free to try, I'll keep it open for now). Locally it both works. My cors config is the default as per below.
Any idea? I'm on an EC2 instance at AWS, running on Nginx.
'paths' => ['api/*', 'graphql'],
'allowed_methods' => ['*'],
'allowed_origins' => ['*'],
'allowed_origins_patterns' => [],
'allowed_headers' => ['*'],
'exposed_headers' => [],
'max_age' => 0,
'supports_credentials' => true,
Please or to participate in this conversation.