# Search UI issues with firewall **URL:** \ **Category:** Elastic Search\ **Tags:** elastic-app-search\ **Created:** [August 6, 2020, 3:03pm UTC](https://discuss.elastic.co/t/search-ui-issues-with-firewall/244052 "2020-08-06T15:03:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![turekg](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@turekg](https://discuss.elastic.co/u/turekg)\ **Post date:** [August 6, 2020, 3:03pm UTC](https://discuss.elastic.co/t/search-ui-issues-with-firewall/244052/1 "2020-08-06T15:03:44Z")
Hello, I am using App Search instance and a user interface based on elastic SearchUi example. I am reverse proxying the nodeja app with Apache. I am using SSL all the way thru to App Search. Everything works fine inside my institute firewall. But from outside the firewall I cannot get this to work. In both case I am using the same URL to access the service. Different browsers report the failure in different ways. However, digging a bit deeper with developer tools the culprit seems to be search.json. In Chrome the error message is "Failed to fetch". The status is ERR\_CONNECTION\_REFUSED. On Firefox, it says "the connection used to fetch this resource" (search.json) is not secure which is confusing everything except elasticsearch itself is running with https. Any ideas? I am really stumped with this. Thanx! ---
**Author:** ![turekg](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@turekg](https://discuss.elastic.co/u/turekg)\ **Post date:** [August 7, 2020, 10:35am UTC](https://discuss.elastic.co/t/search-ui-issues-with-firewall/244052/2 "2020-08-07T10:35:01Z")
OK, I've figured what my problem is... It's the URL to App Search which is not available outside the firewall. Any suggestions on how to deal with this? ---
**Author:** ![turekg](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@turekg](https://discuss.elastic.co/u/turekg)\ **Post date:** [August 10, 2020, 11:05am UTC](https://discuss.elastic.co/t/search-ui-issues-with-firewall/244052/3 "2020-08-10T11:05:29Z")
I've solved this by using the same URL for the searches as the UI and letting the reverse proxy handle the two different paths (one to the UI, the other to App Search) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 7, 2020, 11:05am UTC](https://discuss.elastic.co/t/search-ui-issues-with-firewall/244052/4 "2020-09-07T11:05:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.