We have a barracuda firewall and are trying to present Splunk SH. There is an issue in the way splunk is coded (pr so iots seems) where when using a reverse proxy paths do not exist. If I am on the inside of this firewall I have no issue with this working. Here is the error I am seeing in my browser:
Failed to load resource: the server responded with a status of 404 (Not Found)
https://portal.domain.com/splunk/en-US/i18ncatalog?autoload=1 Failed to load resource: the server responded with a status of 404 (Not Found)
accountpage.js:13 Uncaught TypeError: Cannot set property 'LOCALE' of undefinede.Router.extend.initialize @ accountpage.js:13t.Router @ accountpage.js:9n @ accountpage.js:9(anonymous function) @ accountpage.js:13l @ accountpage.js:6(anonymous function) @ accountpage.js:6
We have our web.conf configured to make splunk root /splunk instead of / .
ANY help is much appreciated.
Hey there sorry for the darkness... Yes it is something like that. It seems that there are hard coded paths in splunk URL's... We have 4 search heads. One 3 node sh cluster and one isolated sh for ES. We have this working for ES (indiv sh) but cannot get it to work with the three node cluster that is load balanced.
Do you see the internal url instead of the public one?
Internally you access splunk.domain.local.
Externally it is splunk.internet
Your browser gets to the front with splunk.internet and then thinks it needs to go to splunk.domain.local?