-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extensions not loading #1
Comments
That's weird. I checked the website 10 hours ago and as you said it wasn't working because of the CORS error. Anyway, thanks for reporting this issue. I'll keep an eye on it. |
I just came to report this very same issue now.. I haven't actually looked at the extensions list before, so I'm not sure when this started happening. from what I can tell by the documentation, it sounds like Amazon AWS doesn't have CORS enabled by default, but if you set up the extensions site like this from the start, then I'm pretty sure you would've enabled it anyway.. maybe there's something funky happening on Amazon's side then? |
I'm using AWS Lambda and it tend to crash like this lately. |
fixed |
A connection error occurs while trying to load the extension list on https://ext.ulauncher.io.
Here's the error copied from my browsers console:
Failed to load https://owd2rwb5be.execute-api.us-east-1.amazonaws.com/prod/extensions: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://ext.ulauncher.io' is therefore not allowed access. The response had HTTP status code 502. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
The text was updated successfully, but these errors were encountered: