It may be helpful to get in contact with the IT team at the Medical Center to add 'https://ep91r43sfk-dsn.algolia.net/' endpoints used by the search engine platform, Algolia, to a whitelist to allow for traffic. Another option is to use a VPN, if applicable and secure, to bypass certain firewall rules.
Algolia currently only supports the two latest version of Chrome, Edge, Firefox, and Safari. The latest stable released version for Chrome is 131.0.6778.109, so it may be helpful to do an upgrade as well.
Hi Scott,
Both the API search key and the index name from your HTML looks fine, so it may not be an search configuration problem. I've made some adjustments to the API configuration for testing purpose, so let me know if that changes anything. Since the search is failing on multiple browser with cache and cookies cleared/disabled, and JavaScript enable, it's an interesting situation. This may be an environment-specific issue so I have a few more questions to get more insights if that's okay.
1. Are there any proxy or firewall being used at the moment? This may affect the API calls. I would try connecting to a different wifi and use the ISC VPN to see if that makes a difference.
2. What version of Chrome/Edge are you using?
3. When using the search bar on a page, does it show the a preview drop down of matched results or just nothing?
4. What's the information listed when you go to the Network tab > Payload?.png)
Hi Scott,
We were able to reproduce the issue you had with an invalid search API key on our end that causes the same blank search page you attached.
Could you send a screenshot when you view the page source of your blank search page?
The functional page on our end currently displays the following:.png)