I'm trying to use the page builder but I'm receiving an error.
If I log into incognito mode, it works for a while and eventually I get this same error. While it's working, I'm going into one of my custom types, and trying to add a link to a prismic page in a field. I select "Link to Prismic Page", and the modal page appears that should let me search for the page, but there's an error below (I can't screenshot it right now) saying something about Unable to query, and when I try to exit/go back into my single use type, I start getting Prismic has encountered an error.
Thanks for the Jam recording, that's really helpful.
It does look like it might be a CORS error. Can you check your VPN/Network settings and make sure that you have https://role.internal.prismic.io/ whitelisted? We've seen it resolve this issue before.
Additionally, check out this troubleshooting guide:
Our company does use netskope and it looks like it might be related. I was able to access it outside of our company computers and make the changes needed.
I'll reach out to our IT team and let them figure out the solution and provide the documentation you mentioned. Thank you!
Hi
We are experiencing the same CORS errors.
This is working on some PC's and some not.
We bypassed all firewall and filter rules to rule out the networking.
In the past forums, it looked like it was a dev issue on the Prismic side. Anything that can get fixed soon?
thank you!
Welcome to the community, and thanks for reaching out!
Can you confirm you have *.internal.prismic.io/* whitelisted, as well as https://role.internal.prismic.io/? When you say some others and some not, are all those PCs on the same networks/VPNs?
We're looking into this at the minute, any information helps
So by bypassing our PC from all filter and network blocks will eliminate the need have anything whitelisted (it is by the way). We didnt see any blockage on the firewall when trying to access the repositories.
They are all on the same network since we are using a firewall VPN to route all traffic to one site.
Thanks for that. Could you give me the name of your repository affected (here or via DMs), and record this behavior with Jam for me? It will give us additional info we can use to troubleshoot this.
Is anyone able to access the repository from a different network, like on mobile for example?