Deployment Architecture

Connecting a search head to indexer through a proxy

Path Finder

I have the following commands in server.conf:

http_proxy =
https_proxy =
no_proxy =, localhost,, ::1

In the web GUI, I try to enter a new distributed search peer, This system is not accessible to splunk through routing, but can be reached by connecting to the proxy for an outbound connection. However, when I attempt to enter the distributed peer in the GUI, I can watch the attempted traffic from the search head and see traffic sent directly on the wire to (which is dropped by the firewall), instead of traffic going to to pass through the proxy.

Has anyone experienced this before, or any ideas why the proxyConfig commands may not be working?
I understand that 80/443 are not the standard/ideal ports for this connection, but that's what I'm working with, and once the connection gets to, I can begin working on the other problems of the ports, but for now, the SH is putting traffic directly onto the network, and not trying to take advantage of the proxy.

|----|          |-----|      |        |-------|
|    |          | 192 |      |(80/443)| 10.15 |
| SH |--------->|168.1|----->|------->| .12.20|
|    |          | .5  |      |        |(idxr2)|
|----|          |-----|      |        |-------|
  |                          |
  | (splunk ports allowed through)
|.1.100 |
0 Karma

Splunk Employee
Splunk Employee
0 Karma
Get Updates on the Splunk Community!

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...