# Troubleshooting: Search errors **URL:** \ **Category:** FAQs\ **Created:** [September 20, 2024, 10:55am UTC](https://community.prismic.io/t/troubleshooting-search-errors/16701 "2024-09-20T10:55:25Z")\ **Posts on this page:** 2\ **Page:** 1
**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:55am UTC](https://community.prismic.io/t/troubleshooting-search-errors/16701/1 "2024-09-20T10:55:25Z")
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.internal.prismic.io](http://document-search.internal.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 Netskope and Zscaler may interfere with the search feature. Disable or reconfigure these as needed. - For one user, CloudFront appeared to be 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. **Step 5: Test and Report** - Please pass this information on to your IT team to investigate these settings and let us know how it goes. ---
**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:55am UTC](https://community.prismic.io/t/troubleshooting-search-errors/16701/2 "2024-09-20T10:55:28Z")