The new search feature in Prismic Repository doesn't work. I've tested it only on my browser - ms-edge, so maybe something's wrong.
This is preventing me from quickly searching for documents that I've created in Prismic.
So we think your company's network or proxy settings might be very strict, and your team will need to whitelist the new domain for our search: document-search.prismic.io
Can you pass this information on to your team?
Can you tell me if your company is using a VPN? If not can you try in different browsers?
I've passed on the message, and will also check this out from my home network to be sure, and let you know earliest by tomorrow.
More reports are coming through that this is related to VPN and local network settings.
For some users it was related to tools such as Netskope and Zscaler.
Please investigate your network settings and let us know how it goes 
Following along
1 Like
The above suggestions have been what has fixed the issue for anyone experiencing it.
For one user, it appeared that CloudFront was seeing multiple source IPs due to how Netskope routes and inspects traffic. To resolve this, a policy was implemented to route all traffic for the domain through a single tunnel, ensuring it originates from a consistent IP.
Please pass this information on to your IT team.
I created a troubleshooting based on this conversation:
It works on my home system. The error is then because of network policies at my office. Sorry for the troubles. 
On further looking into it along with the IT guy at office, I can see that that query does go through and I get a response back from Prismic for the search, but the data isn't displayed. Here's what the response looks like in the network tab:
@Phil can you please look into this. I've created a new jam for easy troubleshoot:
https://jam.dev/c/4a1cca89-fd18-4e00-9b8e-e07933b17b6f
1 Like
Thanks for the update.
While you are able to visit the link directly because it's not 'cross-origin' once you navigate directly, it seems your office network is still blocking it when consumed from the repository because of this 'cross-origin' definition.
What should I do to make this work?????
anything that i need to do specifically to make this work, because I still don't understand the problem. The screenshot is from the prismic page builder. when I search something, the fetch query shows as failed, but when I double click on that failed fetch request, it shows me query results.
here's the console from the page builder itself:
`DialogContent` requires a `DialogTitle` for the component to be accessible for screen reader users.
If you want to hide the `DialogTitle`, you can wrap it with our VisuallyHidden component.
For more information, see https://radix-ui.com/primitives/docs/components/dialog
AXt.console.error @ EditorConfig.ts:147
instrument.js:111 Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}.
(anonymous) @ instrument.js:111
Show 1 more frame
Show less
working:1 Access to fetch at 'https://document-search.prismic.io/?repository=lazylync&searchTerm=netsuite&localeId=en-us' from origin 'https://lazylync.prismic.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
document-search.prismic.io/?repository=lazylync&searchTerm=netsuite&localeId=en-us:1
Failed to load resource: net::ERR_FAILED
EditorConfig.ts:147 RequestError: {
"url": "https://document-search.prismic.io/?repository=lazylync&searchTerm=netsuite&localeId=en-us",
"type": "unknown",
"cause": {
"name": "TypeError",
"message": "Failed to fetch",
"stack": "TypeError: Failed to fetch\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:605:386\n at mt (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:594:116028)\n at $je (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:595:8519)\n at Object.current (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:637:2955)\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:297:9751\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:297:9983"
},
"online": true,
"connectionType": "3g"
}
at mt (Http.ts:101:1)
at async Object.<anonymous> (useDocumentSearch.ts:86:1)
AXt.console.error @ EditorConfig.ts:147
Http.ts:101 Uncaught (in promise) RequestError: {
"url": "https://document-search.prismic.io/?repository=lazylync&searchTerm=netsuite&localeId=en-us",
"type": "unknown",
"cause": {
"name": "TypeError",
"message": "Failed to fetch",
"stack": "TypeError: Failed to fetch\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:605:386\n at mt (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:594:116028)\n at $je (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:595:8519)\n at Object.current (https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:637:2955)\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:297:9751\n at https://lazylync.prismic.io/builder/assets/index-OZbOHsVc.js:297:9983"
},
"online": true,
"connectionType": "3g"
}
at mt (Http.ts:101:1)
at async Object.<anonymous> (useDocumentSearch.ts:86:1)
[NEW] Explain Console errors by usi
```Are you in charge of the network policies in your office?
`We've TeraMind installed for security purposes on the Work Laptop.
See the What, Why, and How for Every User Action - Teramind
I tried accessing the search feature again from my home network, and it didn't work on the Work Laptop on which Teramind is installed.
But it did work on my home computer which doesn't have it installed. Let me know if there's any information available about this, as I'm receiving the response in the console, but then it isn't rendered in the UI.
Also, there's another message in the console I checked just now:
Access to fetch at 'https://document-search.prismic.io/?repository=lazylync&searchTerm=netsuite&localeId=en-us' from origin 'https://lazylync.prismic.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
In that case, it confirms you'll need to play with the settings of Teramind or whitelist anything to do with Prismic on that service, as recommended here.