https://community.splunk.com/t5/Splunk-Search/HTTP-header-connection-failed/m-p/698534#M237190 <P>When we are trying to run a report in deployment server to get the hosts that are reporting to Splunk, it is giving below error</P><UL><LI>Unable to determine response format from HTTP Header</LI><LI>Connection failed with Read Timeout</LI><LI>The REST request on the endpoint URI /services/deployment/server/clients?count=0 returned HTTP 'status not OK': code=502, Read Timeout.</LI></UL><P>Can anyone please suggest any work around.</P> Mon, 09 Sep 2024 09:00:22 GMT anila_ec21 2024-09-09T09:00:22Z https://community.splunk.com/t5/Splunk-Search/HTTP-header-connection-failed/m-p/698534#M237190 <P>When we are trying to run a report in deployment server to get the hosts that are reporting to Splunk, it is giving below error</P><UL><LI>Unable to determine response format from HTTP Header</LI><LI>Connection failed with Read Timeout</LI><LI>The REST request on the endpoint URI /services/deployment/server/clients?count=0 returned HTTP 'status not OK': code=502, Read Timeout.</LI></UL><P>Can anyone please suggest any work around.</P> Mon, 09 Sep 2024 09:00:22 GMT https://community.splunk.com/t5/Splunk-Search/HTTP-header-connection-failed/m-p/698534#M237190 anila_ec21 2024-09-09T09:00:22Z https://community.splunk.com/t5/Splunk-Search/HTTP-header-connection-failed/m-p/698582#M237224 <P>You can override default timeout inside a rest call - add a timeout=300 and see if that helps.&nbsp; &nbsp;You more likely are going to run up against a different error but getting past the timeout issue is the first step to find the underlying issue.</P> Mon, 09 Sep 2024 16:50:17 GMT https://community.splunk.com/t5/Splunk-Search/HTTP-header-connection-failed/m-p/698582#M237224 dural_yyz 2024-09-09T16:50:17Z