For the test, /app/lookup_editor URL was also set to reverse-proxy toward splunk, but it did not work properly, so currently downgraded to v3.6.0. If I connect directly to the splunk using a port without reverse-proxy, it works normally as you said. Thank you. ... View more

Only URLs starting with /splunk are delivered to Splunk through reverse-proxy, so it does not work in my environment. ... View more

For testing, I did a clean install of Splunk enterprise v9.0.5 as a docker image, and got the same results. After the initial installation, I logged in with admin // password and installed the splunk-app-for-lookup-file-editing_401.tgz   - btool results sudo /opt/splunk/bin/splunk btool web list --debug | grep root /opt/splunk/etc/system/local/web.conf root_endpoint = /splunk   - screenshot of test instance ... View more

Since I'm using a free license, I can't seem to open a case. The root_endpoint in the /opt/splunk/etc/system/local/web.conf file is set correctly, and Splunk is working fine. I'm sorry, I didn't write it down clearly enough. If you use Lookup editor v4.0.1, https://splunk_address/splunk/ko-KR/app/lookup_editor/lookup_list page, the links are looking incorrectly like this https://splunk_address/app/lookup_editor/lookup_edit?... They should look like this https://splunk_address/splunk/ko-KR/app/lookup_editor/lookup_edit?... In Lookup editor v3.6.0 and earlier, it looks fine using the root_endpoint value. ... View more