Deployment Architecture

splunk redirecting to 127.0.0.1 instead of primary IP after adding context

aak2
New Member

All,

We are using splunk 6.0 with a distributed enviroinment. since we have 2 search heads we are trying to add 2 seperate context root to both the search heads like /sh01 and /sh02 to have both of them on same apache.

Im trying to accomplish it by following config in local web.conf on search head 01:

[local]

[settings]

httpport = 9000
mgmtHostPort = IP:9089
root_endpoint = /sh1
tools.proxy.on = True

but in browser im getting redirected to 12.0.0.1 instead of the actual IP that sh1 supposed to work. Please help me.

Thanks in advance.

0 Karma

aak2
New Member

I managed to fix this issue by changing tools.proxy.on = True to False.

Thanks Lucas for your help.

0 Karma

aak2
New Member

Am seeing this behaviour from searchhead itlef. we are accessing splunk directly through IP:port combination on browser. I mentioned here as IP on our server we do have the actual IP configures like" mgmtHostPort = 11.22.33.44:9089"

0 Karma

Lucas_K
Motivator

Shouldn't "mgmtHostPort = IP:9089" actually have an IP address? ie "mgmtHostPort =127.0.0.1:8089"

Also as you have proxy.on set I assume you are using apache 1.x?

0 Karma
Get Updates on the Splunk Community!

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...

Adoption of Infrastructure Monitoring at Splunk

  Splunk's Growth Engineering team showcases one of their first Splunk product adoption-Splunk Infrastructure ...

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...