Jade

yeahhh check that ur error responses also include the CORS headers. A common trap: the request reaches the API, the API returns 401 or 500, but the error handler doesnt add CORS headers, so the browser reports a CORS error and hides teh…

Open DevTools Console. Each mixed content warning names the exact insecure URL: Mixed Content: The page at 'https://...' was loaded over HTTPS, but requested an insecure resource 'http://...'. Collect those URLs; the domain and path…

lol same thing happened to me exact same thing happened to my old thinkpad last month hope that helps :)