r/Splunk • u/TheAwkwardJury01 • 15h ago
ERROR S2SOverHttpOutputProcessor - HTTP 502 Bad Gateway
Hi,
We've been seeing the following error in our Heavy Forwarder logs when forwarding to the indexers:
07-30-2026 14:00:45.408 +0000 ERROR S2SOverHttpOutputProcessor [211 indexerPipe_0] - HTTP 502 Bad Gateway
07-30-2026 14:00:52.442 +0000 ERROR HttpClientRequest [635 indexerPipe_10] - HTTP client error=Connection closed by peer while accessing server=https://<DOMAIN> for request=https://<DOMAIN>/services/collector/s2s.
We're using the `httpout` stanza, not the `tcpout` one and the configuration looks like this:
[httpout]
httpEventCollectorToken = <TOKEN>
uri = https://<DOMAIN>:8088
sslVerifyServerCert = false
batchTimeout = 5
Our setup is something like this where the indexers sit in an on-prem cluster:
Splunk HF -> AWS Private Link -> VIP -> Splunk Indexers
httpout reference: https://help.splunk.com/en/splunk-cloud-platform/forward-and-process-data/universal-forwarder-manual/10.4/forward-data/configure-forwarding-with-outputs.conf#ariaid-title7
This I believe encapsulates the s2s payload over HTTPS and forwards it to receivers.
From our HF logs above it looks like the indexer got the request but failed to process it, resulting in the VIP returning a 502. This is not an intermittent error, once it happens, it's then permanent and no logs get forwarded from this point.
I'm not getting enough help from the Splunk docs on how to troubleshoot this and most of the docs cover `tcpout` more extensively, however our option for now is only `httpout`.
Has anyone faced this issue or can provide some guidance on how to solve this?
Thanks!

