Hello,
I can't log into the dashboard with email any more:
The only error is that https://role.internal.prismic.io/team-spaces isn't returning a CORS header. I can open the URL, which returns an empty JSON array, but Prismic can't access it.
Hello,
I can't log into the dashboard with email any more:
The only error is that https://role.internal.prismic.io/team-spaces isn't returning a CORS header. I can open the URL, which returns an empty JSON array, but Prismic can't access it.
Hello @marcellothearcane,
CORS errors are usually related to network settings.
Can you try whitelisting *.internal.prismic.io/*
and let me know if that fixes it for you?
Thank you!
Thanks Ezekiel,
I can access https://test.internal.prismic.io as mentioned here: Important: Test Your Access to Prismic’s New Internal Infrastructure
Also, I can log in with Edge, but not with Firefox (my default).
You mean you're only getting this screen/CORS error on Firefox? Have you tried whitelisting *.internal.prismic.io/*
?
Thank you!
Hang on, I can get onto the main dashboard (https://prismic.io/dashboard) with Edge, but not my site dashboard.
It has the same CORS error for role.internal.prismic.io and billing.internal.prismic.io, which causes the "Prismic has encountered an error" warning.
I can access the URL if I navigate to it in the browser, so I don't think it's blocked...
Thank you for the precision! Are you using Windows or Mac?
If you just click the link/manually access the URL, CORS is not involved. CORS is only involved when that URL is invoked from a different domain, so it wouldn't block it if you're calling it directly.
We're investigating this issue currently, so thank you for reporting it, every little bit of information helps. For the time being I can only ask you to try whitelisting the domain I mentioned above, it seems to have fixed it for some users!
I'll let you know if I have any more information about this issue.
I'm using Windows 10.
The headers from role.internal.primsic.io are:
Content-Length: 14
Content-Type: application/json
Date: Tue, 21 Jan 2025 09:59:59 GMT
Via: 1.1 9e962ebb7744c5eda2db5997b7dde0c6.cloudfront.net (CloudFront)
x-amz-apigw-id: <removed>
X-Amz-Cf-Id: <removed>
X-Amz-Cf-Pop: <removed>
x-amzn-RequestId: <removed>
X-Amzn-Trace-Id: <removed>
X-Cache: Miss from cloudfront
I would expect there to be Access-Control-Allow-Origin: https://mysite.prismic.io
in there as well, and the other CORS headers like Access-Control-Request-Headers
.
Thanks for your help!
@Ezekiel this is now fixed, the following headers are being returned in addition to the above:
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: https://mysite.prismic.io
Thanks for getting back to me! I'm glad this is resolved - we had an issue where a small minority of browsers sent a header in Capitalized case whereas all the others sent it in lowercase, and it was causing us some trouble. Glad our fix is working.