Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

So, I have previously installed Splunk 3.x behind a reverse proxy and downloaded the latest version (4.0.6 at time of typing) expecting it to be as easy to use as before. Sadly this was not the case. There appears to be some elements which are not being translated correctly through the reverse proxy, causing Splunk to fail.

I have used the following configuration in Apache2 to no avail:

<VirtualHost *>
    ServerName monitoringbox.com
    DocumentRoot /path/to/nowhere

    ProxyRequests off
    ProxyPass /splunk http://127.0.0.1:8000/splunk
    ProxyPassReverse /splunk http://127.0.0.1:8000/splunk
    <Proxy /splunk/*>
        Order  allow,deny
        Allow  from all
    </Proxy>

Has anyone else had more luck than me in setting up Splunk 4.x behind a reverse proxy?

share|improve this question
    
Dang, forgot to encode the &lt;VirtualHost&gt; and &lt;Proxy&gt; containers. –  sgerrand Nov 16 '09 at 9:10
    
Double dang! Hit again! –  sgerrand Nov 16 '09 at 9:10
add comment

3 Answers

The key element that needs to be changed in the Splunk web.conf is:


tools.proxy.on = True

All good now.

share|improve this answer
add comment

One of my Splunk installs is behind a reverse proxy. Instructions are over at splunkninja.com: http://splunkninja.com/profiles/blogs/configuring-apache-as-a

share|improve this answer
    
Thanks for the reply - I think there is something more fundamental breaking the proxy behaviour, as you shouldn't need to have three separate rules for {en-US,static,manager}. I think it's more likely to be either the differing root for the Splunk instance or a more complex proxy config is required to ensure that the cookie elements are translated correctly. Off to tcpdump I go. –  sgerrand Nov 16 '09 at 22:41
add comment

I see you are mapping /splunk into /splunk of backend instance, port 8000. I don't know what is the behavior of your version, but ours (4.2) answers directly on /.

Can you try removing the /splunk part of the backend url? Like this:

ProxyPass          /splunk   http://127.0.0.1:8000/
ProxyPassReverse   /splunk   http://127.0.0.1:8000/
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.