# New search blocked by CORS error **URL:** \ **Category:** Prismic for Content Creators\ **Tags:** page-builder\ **Created:** [September 19, 2024, 4:48pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697 "2024-09-19T16:48:07Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mah.psv](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@mah.psv](https://community.prismic.io/u/mah.psv)\ **Post date:** [September 19, 2024, 4:48pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/1 "2024-09-19T16:48:07Z")
Our customers are experiencing a CORS error that prevents the new search from functioning. ![Screenshot 2024-09-06 163756 (1)](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/4/471c2a040bd5321369418d208c450f325e21df78.png) ---
**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\ **Post date:** [September 20, 2024, 10:56am UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/2 "2024-09-20T10:56:27Z")
Hi @mah.psv , I created an troubleshooting guide on how to resolve this 🙂 > [@Troubleshooting: Search errors](https://community.prismic.io/t/troubleshooting-search-errors/16701): > > Here are some steps for resolving network and Cors errors in the search bar and Prismic link component. Step 1: Check VPN and Network Settings Most search issues are related to VPN or local network configurations. Step 2: Whitelist the New Domain Add [document-search.prismic.io](http://document-search.prismic.io) to your whitelist to ensure smooth access. Step 3: Remove SSL Inspection Some teams solved the problem by removing SSL inspection for the entire [prismic.io](http://prismic.io) domain. Step 4: Investigate Security Tools Tools like … ---
**Author:** ![mah.psv](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@mah.psv](https://community.prismic.io/u/mah.psv)\ **Post date:** [September 20, 2024, 3:21pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/3 "2024-09-20T15:21:59Z")
Our clients are large Fortune 50 companies. They are not going to be willing to make these types of changes. Please advise. ---
**Author:** ![mah.psv](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@mah.psv](https://community.prismic.io/u/mah.psv)\ **Post date:** [September 20, 2024, 3:23pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/4 "2024-09-20T15:23:32Z")
Note that the domain is accessible from their network. ---
**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\ **Post date:** [September 20, 2024, 3:51pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/5 "2024-09-20T15:51:14Z")
What steps have they taken to check their VPN settings and security tools in how it relates to Prismic? ---
**Author:** ![mah.psv](https://avatars.discourse-cdn.com/v4/letter/m/eada6e/32.png) [@mah.psv](https://community.prismic.io/u/mah.psv)\ **Post date:** [September 20, 2024, 7:10pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/6 "2024-09-20T19:10:13Z")
We sent a ticket to their IT network and they said they were unable to assist. One client is using Zscaler and we had them disconnect to test off their network in a private browser and still received the same error. ---
**Author:** ![Phil](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/phil/32/14_2.png) [@Phil](https://community.prismic.io/u/Phil)\ **Post date:** [September 23, 2024, 2:59pm UTC](https://community.prismic.io/t/new-search-blocked-by-cors-error/16697/8 "2024-09-23T14:59:59Z")
Thank you for the update. I appreciate the IT team might be currently unable to assist further, but it’s crucial that they continue exploring the remaining options. The fact that a client using Zscaler disconnected and tested in a private browser but still encountered the same error still suggests that network configurations, VPNs, or security settings could be involved. We highly recommend having your IT team review any active VPNs, firewalls, or network security software that could be impacting access. Testing from a different network or using a direct connection without a VPN may also help isolate the issue. At this point, continuing to test these options is essential to narrowing down the root cause. Please let us know the results of further tests or if additional guidance is needed from our side. We appreciate your cooperation in resolving this issue as quickly as possible.